Closed ghost closed 12 years ago
I've never been too convinced by the real world utility of this and the logs could get pretty big eventually. But yeah, why not. People wont miss some megs of disk space per fragsoc.
fsfuse has a fairly flexible disk-logging system. Every module's logging can be en/disabled separately, which is really useful for debugging. Logging calls also specify a severity, and release build log everything of a certain severity and above. I've found it really valuable for recreating the moments before an error - context you don't get from a backtrace. You could ask anyone who submits a bug to submit their log too. Turned up to 11 for debugging though, the logs get huge.
Logging to disk enabled by default. Also removed "/"s from filenames :)
Does this wipe on boot, or have some form of size cap? Just thinking it could potentially get a little out of control over long periods. Although perhaps not too bad if some form of compression were introduced.
It changes log file on each startup. Also these are hypothetical problems that we'll raise an issue for if they become an issue.
Feature request as title.