[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [task #5490] syslog

From: Constantine Kousoulos
Subject: Re: [task #5490] syslog
Date: Wed, 31 Jan 2007 19:13:26 +0200
User-agent: Icedove (X11/20061220)

typo corrections... @!#$&*!!

Thomas Bushnell BSG wrote:
I cannot see any reason why, once the system is up and running, even
proc cannot simply syslog just like anything else, provided it does not
hold internal locks as it does so (and this should be true for *every*
call to syslog anyhow, in whatever program).

I can see how internal locking is important. However, by using
another translator to call syslog instead of the original (eg
logrelay instead of proc) don't we bypass the problem? Syslog does
lock but from within logrelay, leaving proc free to continue doing
whatever was doing. All proc did was send an asyncronous message
to logrelay which i don't think it blocks proc's operation much.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]