4 ms·
The failure more is very different. On log partition disk full log writes will fail, which you favourite logging library might decide to ignore. A misbehaving F
by ithkuil 12y ago
The failure more is very different. On log partition disk full log writes will fail, which you favourite logging library might decide to ignore. A misbehaving FUSE daemon can hang applications that write files and assume it's a local disk.
A smart logger can have a writer thread and a buffer and decide to drop log lines if the logger is too slow. But LoggerFS is meant to be a drop in solution for legacy code, so the concern is perfectly valid.
- cbr 12y agoYou could set up a watchdog.
- rdtsc 12y agoYap one could put a watchdog. And then a status reporting and monitoring system to log the log system failures. At some point in that complexity just reverting to rsyslog would seem like a breath of fresh air. Even with its shortcomings. I have been there, over-designed myself into a hole and then looking back at what was started as a simple 3 step idea now turning into exponentially growing number of branches and corner cases that have to be handled.. Sometimes it is easier to just say "ok this was not a good design" and just throw it away. I have done that and looking back it was a good decision.