Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Re: [PATCH] innfeed does not reopen (rotated) log file
      (Julien ?LIE)


----------------------------------------------------------------------

Message: 1
Date: Mon, 03 Jun 2013 20:29:03 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: [PATCH] innfeed does not reopen (rotated) log file
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Florian,

> feel free to just commit whatever you think is reasonable.

I have just committed revision 9479 for STABLE (INN 2.5.4):
     http://inn.eyrie.org/trac/changeset/9479/branches/2.5

It runs fine on my news server.  Do not hesitate to tell if you see 
something wrong on yours.


The remaining issue was to properly flush channel / exploder feeds after 
rotation so that a deleted log/OLD/errlog was not kept open.  But isn't 
it already solved by the change in "ctlinnd flushlogs"?  This file is 
rotated and then channel and exploder feeds flushed.
Is the problem now only concerning "livefiles" like perl-nocem.log or 
controlbatch.log that are rotated after the feeds have been flushed, or 
do you believe something else needs fixing?

-- 
Julien ?LIE

? A program should always respond to the user in the way that
   astonishes him least. ? (Plauger's Law of Least Astonishment)


------------------------------

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

End of inn-workers Digest, Vol 52, Issue 1
******************************************

Reply via email to