[task #5490] syslog

Update of task #5490 (project hurd): Open/Closed:Open => Closed ___ Follow-up Comment #1:

Re: [task #5490] syslog

At Tue, 30 Jan 2007 15:41:05 -0800, Thomas Bushnell BSG wrote: > 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 transla

Re: [task #5490] syslog

On Thu, 2007-02-01 at 00:22 +0200, Constantine Kousoulos wrote: > > 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 b

Re: [task #5490] syslog

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 general. Keeping things always as RPCs makes the system much more likely to be portable in the future to other kernels. It's n

Re: [task #5490] syslog

On Wed, 2007-01-31 at 19:13 +0200, Constantine Kousoulos wrote: > 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

Re: [task #5490] syslog

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 wh

Re: [task #5490] syslog

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 h

Re: [task #5490] syslog

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

Re: [task #5490] syslog

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

Re: [task #5490] syslog

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

Re: [task #5490] syslog

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.

Re: [task #5490] syslog

Here is my simple translator named logrelay. A first attempt to syslog the proc server could be the following: --- hurd/proc/mgt.c 2003-08-17 01:19:37.0 +0300 +++ mymgt1.c2007-01-29 21:04:45.0 +0200 @@ -18,7 +18,7 @@ the Free Software Foundation, 675 Mass A

Re: [task #5490] syslog

Hi, Constantine Kousoulos, le Wed 24 Jan 2007 13:10:55 +0200, a écrit : > Filesystem logging is a separate issue that i haven't touched yet. > I don't think it's optimal to send messages from the fs to my > translator and then use the fs to write to the log! What if the fs > crashes or malfunction

Re: [task #5490] syslog

Hello all, In order to make the Hurd servers use syslog, i have set up a simple translator that can receive log messages and then call syslog on behalf of the sender. I have experimented with the proc "server" and it seems to be working. What do you think of this approach? Another matter is what

Re: [task #5490] syslog

Hi, On Tue, Nov 28, 2006 at 06:09:58PM +0200, Constantine Kousoulos wrote: > Can you please elaborate which servers you characterise as > "low-level"? Well, all the core servers operating below the POSIX level: task, exec, proc, auth, passwd, pipe... I'm not quite sure about pfinet and ext2 -- t

Re: [task #5490] syslog

Constantine Kousoulos, le Tue 28 Nov 2006 18:09:58 +0200, a écrit : > [EMAIL PROTECTED] wrote: > > Normal programs contact syslog using normal POSIX mechanisms. The > >low-level Hurd servers however work below the POSIX environment -- they > >are responsible for *implementing* these mechanisms. >

Re: [task #5490] syslog

[EMAIL PROTECTED] wrote: > Normal programs contact syslog using normal POSIX mechanisms. The low-level Hurd servers however work below the POSIX environment -- they are responsible for *implementing* these mechanisms. You need to find a way for syslog to get information from the low-level serve

Re: [task #5490] syslog

Hi, On Mon, Nov 27, 2006 at 10:11:13PM +0200, Constantine Kousoulos wrote: > From http://savannah.gnu.org/task/?5490: "Find and implement a > suitable way to make the Hurd servers use `syslog'. " > > Can someone explain what this task demands to be done? > > Debian's syslogd seems to be working

Re: [task #5490] syslog

Hi, Constantine Kousoulos, le Mon 27 Nov 2006 22:11:13 +0200, a écrit : > I understand that syslogd cannot act as klogd does in linux. ? syslogd already reads /dev/klog and puts that into /var/log/kern.log . If it does not any more, it's just a bug. Samuel

Re: [task #5490] syslog

Barry deFreese wrote: Constantine, AFAIUI, the task IS to make Hurd code write entries to syslog. ITAIT, i'm on it! (ITAIT = If That's All It Takes :) ) Thanks, Constantine ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mail

Re: [task #5490] syslog

Constantine Kousoulos wrote: Hello again, From http://savannah.gnu.org/task/?5490: "Find and implement a suitable way to make the Hurd servers use `syslog'. " Can someone explain what this task demands to be done? Debian's syslogd seems to be working with the current GNU/Hurd snapshot. To t

[task #5490] syslog

Hello again, From http://savannah.gnu.org/task/?5490: "Find and implement a suitable way to make the Hurd servers use `syslog'. " Can someone explain what this task demands to be done? Debian's syslogd seems to be working with the current GNU/Hurd snapshot. To test it, i added a few syslog e

[task #5490] syslog

URL: Summary: syslog Project: The GNU Hurd Submitted by: tschwinge Submitted on: Tuesday 04/25/06 at 15:37 Category: The GNU Hurd Should Start On: Tues