On Mon, 8 Nov 2004 10:07:58 +0000 Dominic Hulewicz <[EMAIL PROTECTED]> wrote:
> Due to the low LogFileMaxSize limit I have set in clamd.conf, my clamd > log file occasionally hits the maximum size and correctly reports > "LOGGING DISABLED (Maximal log file size exceeded)". > > A weekly logrotate script renames clamd.log and SIGHUP's the clamd > process, but this does not restart logging again as I anticipated. > Does it really require a total restart in order to reinstate logging? Yes, it does. Thanks for pointing out this problem. -- oo ..... Tomasz Kojm <[EMAIL PROTECTED]> (\/)\......... http://www.ClamAV.net/gpg/tkojm.gpg \..........._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Mon Nov 8 11:12:32 CET 2004
pgpOsg7IYiaZ0.pgp
Description: PGP signature
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
