Dealing with disk I/O problems

Posted Jul 1, 2005 12:59 UTC (Fri) by ringerc (subscriber, #3071) [Link]

Chances are that if you've ever tried to write a program to parse the system log and notify the user of errors, it'd be fairly obvious why. Doing so is a screaming nightmare.

Having important messages broadcast out over D-Bus could be a really nice feature. Apps could listen only to messages they care about, without having to follow a log that's potentially full of reams of crud. It should be possible to do it much more reliably than tailing syslog, too.

I can see why folks would be concerned about the duplication of functionality, but I tend to see syslog (or at least klog) as a dinosaur that might be in need of a replacement. Preferably a replacement that can still write out syslog, but can also give programs access to the errors in a more useful way. This is one thing the Windows folks have the right idea with IMO - though their own implementation has its (large) fair share of issues, too.

Posted Jul 6, 2005 18:22 UTC (Wed) by zakaelri (guest, #17928) [Link]

It seems to me that if you are having a problem with a filesystem, it would not always be the best idea to log the request in a file...

I appologize for sounding snippety. I'm spending far too much time on /.