On Fri, Apr 11, 2008 at 08:00:09AM +0200, Gian Piero Carrubba wrote: > assumption), so maybe the problem is that, for whatever > reason, syslogd is restarted instead that signalled...
maybe - check (also) logrotate actions. Or switch to other *log solutions - eg the -ng mentioned or socklog. -- paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
