Re: stopping multilog

On Mon, 29 Sep 2008 12:19:30 -0400
[email protected] (Paul Jarc) wrote:

> richard lucassen <[email protected]> wrote:
> > #!/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" s16777215 n2 ./eth1
> >
> > Is processor2 executed after processor1? Or are they invoked
> > simultaniously?
> 
> They run sequentially.  It's done in lines 454-459 in multilog.c.

Ok, thnx Paul. As I mentioned in my reply to Otavio I send an ALARM to
the multilog process. 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?:

#!/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" s16777215 n2 ./eth1 \
  !/path/to/script-that-runs-after-the-other-processors 

-- 
___________________________________________________________________
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                         |
+------------------------------------------------------------------+