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? Thanks, Dominic. _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
