[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: Thu, 01 Feb 2007 00:22:21 +0200
User-agent: Icedove (X11/20061220)

Thomas Bushnell BSG wrote:
We generally tend to dislike the use of asynchronous messages.  They are
great for Mach, but we would like to avoid the need to use them in

Keeping things always as RPCs makes the system much more likely to be
portable in the future to other kernels.

It's nice to know the direction the implementation is headed. I would be grateful if you could supply links that further document the above mentioned statement. To be honest, i had the exactly opposite idea since it has been mentioned that the Coyotos kernel was a candidate to replace the Mach kernel and Coyotos has an asynchronous design.

Regarding the syslog problem, what can be done? From what has been said so far, the intermediate translator solution is not optimal. Do we use syslog as it is but carefully because of the internal locking? If so, this task should be deleted.

How about this: what if the syslog daemon was rewritten as a syslog translator capable of handling the locking issue?


reply via email to

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