Various things on log_net package

[Rene Wittmann]

Hi Jork,

On Fri, Apr 08, 2005 at 06:56:02PM +0200, Jork Loeser wrote:
> Hi Rene,
> 
> > While trying to get the log server working for logging to network, I
> > found some problems/bugs...
> 
> Thank you for the hints. Actually, I am leaving the group, and I am not
> shure whether the net-log is a priority project someone is willing to
> spend time on maintaining. Nonetheless, your remarks are well conserved,
> and patches are welcome.

Maybe it's priority is not that high, but I think it's an easy to use
log mechanism, especially when you don't want to do just debugging but
some analysis of the "real" behaviour of your code.
So as soon as I find time I will propose some patches.

> 
> > Problem when using the logging to network within a program that uses the
> > parse_cmd library
> 
> This is strange, indeed. The log output, appears it normally, or does it
> have an asterisk in front? The fall-back of the log-lib is to output the
> data locally, if no log server is found within some time interval (both
> local log-server and networked version).  Although, this fall-back will be
> indicated with an '*' in front of each line.

No, it's seems to be no fall-back as there are no '*''s. The logserver
says that it will output to net, but does only output locally (even when
said '-nolocal'. And as said before no '*'.

> Further, is the output of every program local, or only that of the one
> using the parse_cmd lib?

I use not really another program, my grub config looks like this:

title vmware rt_sched deadline miss .211 
	root (hd0,1)
	kernel /drops/drops/bin/x86_586/l4v2/rmgr -sigma0
	module /drops/l4/kernel/fiasco/build/main -nokdb -nowait -serial -serial_esc -vmware
	module /drops/drops/bin/x86_586/l4v2/sigma0
	modaddr 0x02000000
	module /drops/drops/bin/x86_586/l4v2/names
	module /drops/drops/bin/x86_586/l4v2/log_net_lance -verbose -net -nolocal -ip 131.188.36.211 -buffer 4096
	module /drops/drops/bin/x86_586/l4v2/dm_phys
	module /drops/drops/bin/x86_586/l4v2/rt_sched -l -m

(but even saying '-local' instead of '-nolocal' in log_net_lance gives the same
behaviour)



BTW: maybe writing to a file locally for logging would be easier, but as
far as I know there is no possibility to do so in DROPS?

Kind Regards,
Rene