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??
On Sat, 2006-12-09 at 09:43 -0600, Mikkel L. Ellertson wrote:
Ted Gervais wrote:
I just noticed that while I was working in a terminal screen (F1), not in the GUI that I got a bunch of stuff slowing popping up across my screen. And at the time I had nothing working or running in the GUI setup. Here is what I saw. Wondering what it meant??
<------------[ SNIP ]--------------->
They look like system console messages. They should be handled by syslogd/klogd, not displayed on the console. Double check that syslog is running. (service syslog status)If it is running, you may want to take a look at /etc/syslog.conf - you should only have one line that just has * in the right column.
# Everybody gets emergency messages *.emerg *
Mikkel
Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!