stopping syslog errors from vserver guests

2009-03-24 Thread Anton Piatek
Hi, Following on from the below message where I found that some of my vserver guests are causing errors to be written in the vserver host's syslog, does anyone know if/how it is possible to stop certain errors from appearing? 2009/3/23 Anton Piatek an...@piatek.co.uk: 2009/3/23 Anton Piatek

Syslog errors in Lenny from gkrellmd

2009-03-23 Thread Anton Piatek
Not sure when these errors started, but I have recently been seeing errors in my syslog like the following: Mar 23 13:55:05 dementia kernel: [ 8535.882191] vxW: [�gkrellmd�,4613:#40002|40002|40002] did lookup hidden 8103f59eeb08[#0,4026531859] �/proc�. Mar 23 13:55:05 dementia kernel: [

Re: Syslog errors in Lenny from gkrellmd

2009-03-23 Thread Anton Piatek
2009/3/23 Anton Piatek an...@piatek.co.uk: Not sure when these errors started, but I have recently been seeing errors in my syslog like the following: Mar 23 13:55:05 dementia kernel: [ 8535.882191] vxW: [�gkrellmd�,4613:#40002|40002|40002] did lookup hidden 8103f59eeb08[#0,4026531859]

Re: syslog errors

1997-01-13 Thread Tim Sailer
In your email to me, Walter L. Preuninger II, you wrote: Last night while trying to figure out why cron was not starting up, there were no S89cron files in /etc/rc[2-5].d, something happened to my syslog. Now all I get is Jan 12 13:39:47 walterp kernel: klogd 1.3-0, log source = /proc/kmsg

syslog errors

1997-01-12 Thread Walter L. Preuninger II
Last night while trying to figure out why cron was not starting up, there were no S89cron files in /etc/rc[2-5].d, something happened to my syslog. Now all I get is Jan 12 13:39:47 walterp kernel: klogd 1.3-0, log source = /proc/kmsg started. Jan 12 13:39:47 walterp syslogd 1.3-0#11: restart. Jan