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??
printk: 137964 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 861120 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 930424 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:001af951 printk: 359880 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 306447 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 540165 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 472922 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 1097844 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 946617 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:001af581 printk: 770387 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cbff printk: 1163086 messages suppressed. 4gb seg fixup, process beagle-build-in (pid 3861), cs:ip 73:0811cb2a
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
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!
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
On Sat, 2006-12-09 at 16:27 -0500, Jim Cornette wrote:
If you want to stop the beagled service, you can stop it from system/administration/server settings/services under the menu.
And if you don't use it, you may as well un-install it. One less thing on the system...
I had a beagle RPM, but didn't have any beagled service. I haven't really looked into whether that's installed separately. I've un-installed the beagle RPM, and didn't find anything else.
Tim wrote:
On Sat, 2006-12-09 at 16:27 -0500, Jim Cornette wrote:
If you want to stop the beagled service, you can stop it from system/administration/server settings/services under the menu.
And if you don't use it, you may as well un-install it. One less thing on the system...
I had a beagle RPM, but didn't have any beagled service. I haven't really looked into whether that's installed separately. I've un-installed the beagle RPM, and didn't find anything else.
I went a little further and removed all that is dependent upon mono. I guess that is a different issue though. Beagled does not exist on my systems by choice.
Jim
This is a known libc configuration mismatch between stock Fedora Core 6 and Xen/Fedora. See: http://lists.xensource.com/archives/html/xen-users/2006-11/msg00034.html [1]
To fix (quoting from the link above): echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf in your Xen domU
Links: ------ [1] http://lists.xensource.com/archives/html/xen-users/2006-11/msg00034.html
Quote: If you want to stop the beagled service, you can stop it from system/administration/server settings/services under the menu. This does not work for me. (You can get the same prog by starting beagle-settings in a terminal.)
I stopped beagle in FC6 with KDE by removing this file: /etc/xdg/autostart/beagle.desktop Then reboot the computer.
-
Jim Cornette -
Mikkel -
potat0 -
Ted Gervais -
Tim