Critical bug, please fix! Having a log would help a lot when doing remote check disk.
At the very least, telling why it's not important would be a first step instead of just ignoring this bug for the past 6 years. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/513644 Title: Does not log fsck invocations in /var/log/fsck/ Status in mountall package in Ubuntu: Triaged Bug description: Binary package hint: mountall This concerns mountall 1.0 in Karmic. After fsck is invoked at boot time, the two log files in /var/log/fsck/ remain empty. In Jaunty, the /etc/init.d/check{fs,root}.sh scripts saved the output of the commands to that directory ("A log is being saved in ${FSCK_LOGFILE} if that location is writable") but mountall has yet to do this. As this would have to be newly implemented, I'd like to request a slight change from the Jaunty behavior, and have entries be appended to the log files rather than the files being overwritten each time with the latest (single) entry. Log rotation on these files may be good, too, although I'm not sure which package would/should be responsible for that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/513644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
