On Wednesday 06 September 2006 17:15 terry white's cat, walking on the keyboard, wrote: > ... ciao: > : on "9-6-2006" "Luca Ferrari" writ: > : the syslogd daemon crashes > > at one time i had a similar problem with klogd. the first thing i did > was to determine "when" it 'had' stopped running. > > in your case, i think it important to discover if the daemon has > "been" stopped, or, as you say, "crashed". i used cron to test for a pid > every minute. in my case, i noticed a specific time when the failure > occurred. that's a good thing to notice ... I've found the problem: the daemon.log file was too big (and there's no rotate on it), thus the first application that tried to log on such file caused syslogd to crash. Thanks, Luca - To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
