Michael> I´ve found that teh syslog-messages from scotty will go to
Michael> the NT eventlog when I use scotty for win32. I normaly use a
Michael> very good syslog-daemon on NT, because for hetereogenous
Michael> networks it more flexibile.
:-)
Michael> It is possilbe to redirect the syslog-messages from scotty
Michael> win32 to syslog?
There are currently two implementation for writing log messages. The
first one is in win/tnmWinLog.c and uses the Win32 event reporting
facilities and the second one is in unix/tnmUnixLog.c and uses the
Unix syslog facilities. If you want to use unix/tnmUnixLog.c on Win32,
you need to compile this module into the Tnm extension and you have to
supply emulations for the openlog(), syslog(), closelog() functions.
If there are lots of people who prefer to generate syslog messages on
Win32, then I am willing to make code changes so that you can probably
configure on Win32 whether syslog is being used or the native event
log.
(Another option would be to use syslog in general and to ship a small
Win32 service which receives syslog messages and puts them into the
Win32 event log. This solution would move the difference out of the
Tnm extension and the syslog service might be useful for other
purposes as well.)
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.