Re: stopping multilog

richard lucassen <[email protected]> Tue, 30 Sep 2008 23:56:34 +0200
Newsgroups gmane.comp.djb.syslog
Organization XAQ Systems
Message-ID <[email protected]>
On Mon, 29 Sep 2008 12:43:53 -0400
[email protected] (Paul Jarc) wrote:

> richard lucassen <[email protected]> wrote:
> > I want to start a script /after/ the two processors have done their
> > job. So, is adding a third processor the right way to achieve this?:
> 
> Each processor only gets used for the directory that follows it.  So
> if you specify a processor with a directory after it, that processor
> will never be used.  You could do something like this:
> 
> #!/bin/sh
> exec 2>&1
> 
> exec /usr/local/bin/multilog \
>   '-*' '+*mark=384*' \
>   !"/root/dynfw3/conntrack/log/processor1" s16777215 n2 ./eth0 \
>   '-*' '+*mark=387*' \
>   !"/root/dynfw3/conntrack/log/processor2;
>     /path/to/script-that-runs-after-the-other-processors" s16777215 n2
>     ./eth1 \
> 
> Each processor is run by passing the string to /bin/sh -c, so multiple
> commands like this is ok.  Note that if the eth1 log fills up and gets
> rotated before SIGALRM comes, then those last two ocmmand will both
> run, even if there's nothing new to do for the eth0 log.

The whole thing works like a charm now. Thank you Paul and Daryl,
your contributions are really very appreciated :)

R.

-- 
___________________________________________________________________
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+------------------------------------------------------------------+
| Richard Lucassen, Utrecht                                        |
| Public key and email address:                                    |
| http://www.lucassen.org/mail-pubkey.html                         |
+------------------------------------------------------------------+