|
Merrick Moose
Registered User
Join date: 20 Oct 2005
Posts: 191
|
08-01-2006 18:34
Currently the SL client is logging to /bar/log/messages /var/log/syslog and /var/log/user.log Does it really need to be doing that? That's quite a few duplicate logs that it sends not just errors to but also running messages/status messages. Perhaps masking some of these messages or directing them to a single log or /dev/null?  |
|
Kel Hartunian
Reformed Solipsist
Join date: 6 May 2006
Posts: 28
|
08-01-2006 18:42
Is your concern about disk space, processor load or asthetics (cleanness of implementation, et al)?
It would seem a bit extreme if all of those logs were being given exactly the same output. Could be a "we're in alpha, log like crazy for debugging" type of mentality.
|
|
Merrick Moose
Registered User
Join date: 20 Oct 2005
Posts: 191
|
08-01-2006 18:48
From: Kel Hartunian Is your concern about disk space, processor load or asthetics (cleanness of implementation, et al)?
It would seem a bit extreme if all of those logs were being given exactly the same output. Could be a "we're in alpha, log like crazy for debugging" type of mentality. It is terribly dirty and makes it hard to sort out of the client has a bug itself, or if it is a bug in another piece of software. Logging three times is a bit of a waste, it should be cleaner than that I'd say. Load or disk space isn't a problem, though going through a log file looking for a bug is certainly slower when there are matching messages that are not the bug. |