The syslog facility could be implemented as follows:
The program which starts a translator opens /dev/klog on the
translator's behalf and inserts the file descriptor into the
translator's stdout and stderr. This requires modifying settrans,
libdiskfs, etc. but not every translator individually.
Hi,
On Tue, Jan 30, 2007 at 09:30:32PM +0100, Neal H. Walfield wrote:
> The syslog facility could be implemented as follows:
>
> The program which starts a translator opens /dev/klog on the
> translator's behalf and inserts the file descriptor into the
> translator's stdout and stderr.
[...]
An
I see no reason why we should care about emulating klog.
Hurd translators can, in general, perfectly well simply write directly
to the regular /dev/log socket in the regular way. Heck, even the
filesystem and pflocal translators can do so, since they are properly
multi-threaded.
The only issue t
On Wed, 2007-01-31 at 00:03 +0100, [EMAIL PROTECTED] wrote:
> An interesting idea, though it doesn't really help with the problem at
> hand: This thread (and I think the task it refers to) isn't about
> logging from normal translators (which wouldn't need any special
> facility to use syslog() in t
