--- Alexandre Julliard [EMAIL PROTECTED] wrote:
Syslog is for logging system events, which is precisely what Windows
event logging does, so it sounds like a pretty good fit to me.
Maybe WINE should develop a event log service like in WinNT/2k so you
dont have to be root to see these messages.
Hi Alexandre,
What was wrong with this patch? I guess you want it in a separate debug
channel, yes?
On Sun, 2003-10-19 at 12:58, Mike Hearn wrote:
This implementation is obviously not complete, but it prints out the
event log strings using MESSAGE, which is good enough for now. This is
handy
Mike Hearn [EMAIL PROTECTED] writes:
What was wrong with this patch? I guess you want it in a separate debug
channel, yes?
That would be one way to do it, yes. A better equivalent of the
Windows functionality would probably be to use syslog. Using MESSAGE
is definitely wrong.
--
Alexandre
On Sun, 2003-11-02 at 23:20, Alexandre Julliard wrote:
That would be one way to do it, yes. A better equivalent of the
Windows functionality would probably be to use syslog. Using MESSAGE
is definitely wrong.
What's wrong with it? My main concern over other methods is that nobody
would ever
Mike Hearn [EMAIL PROTECTED] writes:
What's wrong with it? My main concern over other methods is that nobody
would ever notice the app was outputting potentially useful information.
At least with MESSAGE there's no chance of people missing it.
And if the info is not useful, there's no way to
If we use the syslog, doesnt this mean we must be root to read the
messages ?
Syslog is for logging system events, which is precisely what Windows
event logging does, so it sounds like a pretty good fit to me.
=
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
ICQ
On October 19, 2003 07:58 am, Mike Hearn wrote:
This implementation is obviously not complete, but it prints out the
event log strings using MESSAGE, which is good enough for now.
Another option is to create a new debug channel (call it eventlog)
and output to it. This way we give people a bit
