> The one downside with using `syslog' is that you wouldn't see the > messages from inside GDB when debugging under GDB. You would instead > need to have a different terminal open to view the contents of the > system logfile. (At least, the only way I currently know to view the > output of `syslog' is to `tail -f /var/log/message' as root, which is > undesirable for multi-user installations.)
Afaik, you can write syslog entries to any file you like, including the console. However, root has to set this up, which is a drawback. > So I'm not sure if `syslog' is a better solution. However, I don't know > much about `syslog' either, so I'm interested in hearing more. However, > it seems that `System.Diagnostics.EventLog' and related classes would > probably be a closer fit to `syslog' than the `Trace' and `Debug' > classes. I think you're right about that. For unix systems I think you have to explicitely add your own trace listener to the code. Greets, Lawrence _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
