Ted Gervais wrote:
I checked out my log on this matter but I discovered something else. I found that these errors occurred right after the GUI screen was brought up. Here is what I found in ' ps ax ' :
6806 ? Sl 0:02 beagled /usr/lib/beagle/BeagleDaemon.exe --autostarte
4gb seg fixup, process beagled (pid 6806), cs:ip 73:00a7fbd9 4gb seg fixup, process beagled (pid 6806), cs:ip 73:0811cbff 4gb seg fixup, process beagled (pid 6806), cs:ip 73:00f92841 4gb seg fixup, process beagled (pid 6806), cs:ip 73:0811cbff 4gb seg fixup, process beagled (pid 6806), cs:ip 73:00f92841 4gb seg fixup, process beagled (pid 6806), cs:ip 73:0811cbff
6905 ? Sl 0:23 beagled-helper /usr/lib/beagle/IndexHelper.exe
6806 ? Sl 0:06 beagled /usr/lib/beagle/BeagleDaemon.exe --autostarte
What is the beagled process? This is very strange to me and what and why is it being started??
Beagled is a process that is supposed to give searching for files an updated database for file locations to aid in searching for files. I do not use beagled myself and rely on updatedb and the locate command.
If you want to stop the beagled service, you can stop it from system/administration/server settings/services under the menu.
Jim