On Fri, 12 Mar 2004 09:33:41 -0500
Betsy Schwartz <[EMAIL PROTECTED]> wrote:
> Would try the CVS version but I am still having trouble building the
> libmilter piece of the distribution, posted the error here last week, so
> I'm using the CSW precompiled packages.
>
Using the same library pac
At 08:44 AM 3/12/2004, Devin Rubia wrote:
If you don't want to go to CVS, you could always use the copytruncate
option in logrotate. Be warned, you could lose a couple of log entries
between the copy and the truncate. Check the manpage for details.
Thanks I will try that. I am on Solaris 8 btw.
On Fri, Mar 12, 2004 at 08:46:19AM +, Trog wrote:
> On Fri, 2004-03-12 at 03:48, Betsy Schwartz wrote:
> > When you say clamAV works with logrotate, what command are you issuing to
> > get clamav to start using the new file? What I'm seeing is that it doesn't
> > respond to SIGHUP but has to
On Thursday 11 March 2004 09:48 pm, Betsy Schwartz wrote:
> When you say clamAV works with logrotate, what command are you issuing to
> get clamav to start using the new file? What I'm seeing is that it doesn't
> respond to SIGHUP but has to be killed and restarted to get it to let go of
> the old
On Fri, 2004-03-12 at 03:48, Betsy Schwartz wrote:
> When you say clamAV works with logrotate, what command are you issuing to
> get clamav to start using the new file? What I'm seeing is that it doesn't
> respond to SIGHUP but has to be killed and restarted to get it to let go of
> the old file
When you say clamAV works with logrotate, what command are you issuing to
get clamav to start using the new file? What I'm seeing is that it doesn't
respond to SIGHUP but has to be killed and restarted to get it to let go of
the old filehandle
Betsy Schwartz
>At 12:41 PM 3/11/2004, John Jolet wrote:
>>why not just run logrotate and have done with it?
>
>It would help if clamd took a "kill -HUP" and started a new logfile.
>
>Betsy Schwartz
Depending on traffic, and logging options selected, this can grow fairly
quickly. If log entries are lost, debuggi
