[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log
Subject:    Re: What's wrong with my !processor script?
From:       prj () po ! cwru ! edu (Paul Jarc)
Date:       2003-03-13 21:40:53
[Download RAW message or body]

Erwin Hoffmann <feh@fehcom.de> wrote:
> Snip. Two different tasks
>
> (1) Either you want analyse your log thru your !processor directive -or-
> (2) you want to backup your log.
>
> Within ONE log-dir thats not possible (IMHO).

Why not?  The processor can do as much work as you like.

> In shell notation, !processor does the following:
>
> processor <&0 current 1> @40000000xxxx.s 5> state

No, it's actually more like:
sh -c 'processor' 0< current 1> @40000000xxxx.s 4< state 5> newstate
mv -f newstate state

Although there is actually more use of temporary filenames and
renaming.

> At 17:51 13.03.03 +0200, Alexander Plakidin wrote:
>> foreach($message as $line){
>>         fputs($logfilep, $line);
>>         echo $line; // for multilog?
>> }

If you don't care about the @*.s files, you don't have to copy the
file to stdout.


paul
[prev in list] [next in list] [prev in thread] [next in thread]