From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Ferrari Subject: Re: syslog problem Date: Tue, 26 Sep 2006 16:12:30 +0200 Message-ID: <200609261612.30917.fluca1978@infinito.it> References: <200609061542.53394.fluca1978@infinito.it> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline Sender: linux-admin-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-admin 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