[BusyBox] Syslogd

[Erik Andersen]

On Tue Mar 06, 2001 at 05:31:16PM -0500, Gennady Feldman wrote:
> 
> On Tue, 6 Mar 2001, Erik Andersen wrote:
> 
> >
> > A rewrite to use select would be a very good thing.
> > By all means, go for it.
> >
> >  -Erik
> 
> One more thing. It seems that syslogd also contains klogd which uses
> logMessage() directly. Is it possible to make it a client of syslogd? The
> problem is that klogd uses blocking call to listen for incoming messages.
> For my case it's still 2 threads/2 writers/1 fork and I still have to keep
> a count of how many writers I have. If we have select() and klogd somehow
> be the client of syslogd then I have 1 thread/1 writer. I am actually
> looking at logger.c which uses client interface to log syslog messages.
> Which just brings me to another point, if we rewrite klogd we can make it
> a separate c file?

Yes absolutely.  I've been very unhappy with myself for glomming those two apps
together.  They really should be seperated.

If we make the syslog client code into library code in utility.c (soon to be
libbusybox) then we can have a separate klogd.c file and both klogd.c and
logger.c can use the same underlying syslog client code.  That will result
in a much cleaner architecture.

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--