On Monday 08 March 2004 17:53, you wrote:

> Shoot, I was hoping you wouldn't notice that point! ... Actually my idea
> only addresses one way of registering a way of selecting then setting
> the channel, all the work you were going to do would still be required,
> but my idea might interfere with yours... unless you had a separate
> command ns_log_tochannel, for instance that would be the underlying
> command???
> Or maybe a better idea is to come up with a way of establishing a
> hierarchy of commands/script files and log based on that criteria
> instead. If procs were namespaced, a message from a certain namespace
> could trigger the desired action. Or while loading, library commands
> could be associated with the files where they were stored...
> Dunno, but your idea of logging to separate channels sounds very good.

Oh, my little idea is evolving :)

Maybe I should point out again the basic motivation behind
it, so we do not miss it as we go...

The idea was to keep the ns_log as-is, i.e. not try to cope
with spreading it (or splitting it on any key) to multiple files.
I needed only to *swap* the current log sink and re-route log-data
somwhere else (possibly to a Tcl socket). This way I can accumulate
logs from various AS instances on one central place by simple Tcl
channel transport, w/o any other helpers (syslog or similar).

Now, the idea evolves and a new task is dawning: how to manage
i.e. better organize the log information itself?
To be honest I did not want to tackle this problem yet. It is
a complex one requiring much more preparation, thinking and coding.

I think that those two above do not exclude themselves. That is,
being able to tell ns_log where to send log-data is one thing
whereas filtering and organizing log which is sent to ns_log is
another, possibly higher level stuff.

Zoran


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of 
your email blank.

Reply via email to