On Fri, Oct 06, 2000 at 07:07:11PM +0200, Harald Hanche-Olsen wrote:
> + [EMAIL PROTECTED]:
>
> | On Fri, Oct 06, 2000 at 06:06:51PM +0200, Harald Hanche-Olsen wrote:
> |
> | > using a <service>/log directory, just have a cron job kill the logger
> | > using svc -t. Supervise will start a new logger. Now, unless you do
> |
> | That's the thought I had too, but I'd want to check that supervise
> | re-establishes the same pipeline between the two processes.
>
> svscan takes care of that by keeping the file descriptor to both ends
> of the pipe open.
Indeed. Of course svc -t doesn't propogate back up to svscan, instead
supervise (which has inherited the pipe) merely re-forks multilog.
In any event, using Harald's strategy works just fine. svc -t the log
service at midnight or whenever, and your job is done.
If you insist on just one file per time period (day) then you'll need
to discourage multilog from automatically rolling by making the size
setting absurdly large. Of course by doing this you remove a major
advantage of multilog, namely resource control.
Regards.
