On Mon, 2004-11-08 at 10:14, Tomasz Kojm wrote: > 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.
Well, it should rotate the log file on a SIGHUP, and indeed does on the two systems I do it on. -trog
signature.asc
Description: This is a digitally signed message part
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
