[Fwd: Re: [SLE] How to start a computer remotely - generic Q]
did it again..I keep forgetting that reply sends a private email. Sorry Dimitri
this is the syslog.conf # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* -/var/log/maillog # Log cron stuff cron.* /var/log/cron # Everybody gets emergency messages *.emerg * # Save news errors of level crit and higher in a special file. uucp,news.crit /var/log/spooler # Save boot messages also to boot.log local7.* /var/log/boot.log and the syslog is Jul 17 14:08:58 LIINFBW syslogd 1.4.1: restart. Jul 17 14:09:03 LIINFBW kernel: klogd 1.4.1, log source = /proc/kmsg started. do you have any idea? the OS is SuSE 9.0 SP 3 Linux LIINFBW 2.6.5-7.244-bigsmp #1 SMP Mon Dec 12 18:32:25 UTC 2005 i686 i686 i386 GNU/Linux --------------------------------- Yahoo! Music Unlimited - Access over 1 million songs.Try it free.
On Monday 17 July 2006 21:15, Alex Hayes wrote:
Jul 17 14:08:58 LIINFBW syslogd 1.4.1: restart. Jul 17 14:09:03 LIINFBW kernel: klogd 1.4.1, log source = /proc/kmsg started.
This in itself doesn't show the "every 30 minutes" claim. But if it really does restart every half hour, do you perhaps have a huge amount of log messages coming in, and have set logrotate to run more than once per day? A crash of syslog wouldn't cause it to restart, there is no respawn functionality that I'm aware of, so it must be something that is actively restarting it, and the only causes I can think of off hand are reboots and log rotating -- Ut supra post festum sunt obscura -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Alex Hayes -
Anders Johansson -
Arun Mallikarjunan