Re: remote logging via socklog/multilog + Zebedee

On Fri, 3 Sep 2004 10:43:54 +0800
Adrian Ho <[email protected]> wrote:
>
> On Thu, Sep 02, 2004 at 02:36:49PM -0700, Aldasair Grhone wrote:
> > Please correct me if I'm mistaken, but what seems to be required is a
> > change in architecture.  multilog should allow the writing of its logs
> > to a processor indefinitely, without having to spawn a new processor
> > every X bytes.  This would allow a persistent network connection to
> > exist and for all data to get written to the log server as it arrives.
> 
> But could cause multilog (and therefore whatever's logging to it) to
> block if the processor stops reading its input for whatever reason.
> 
> What you require is probably better served by a tool that pipes stdin
> to multiple processes simultaneously (in your case, multilog and
> tryto/tcpclient), and that doesn't block on all if one stops reading.
> Something, IOW, like multipipe <http://untroubled.org/qlogtools/>.

Great!  I tried this and it works perfectly.  This does exactly what
I need.

Many thanks!

  Aldasair