Looks like the bug is here in /usr/lib/update-notifier/update-motd-fsck-
at-reboot:
# check time when we did the last check
stamp="/var/lib/update-notifier/fsck-at-reboot"
if [ -e "$stamp" ]; then
stampt=$(stat -c %Y $stamp)
else
stampt=0
fi
now=$(date +%s)
if [ $(($stampt + 3600)) -lt $now ] || [ $stampt -gt $now ]; then
#echo $stampt $now need update
NEEDS_FSCK_CHECK=yes
fi
If you log in on console triggering a refresh of the file, then reboot
and get the fsck, then log in again once the system finishes booting,
there will be a current stamp file and the check will not be re-run.
We should probably compare the file's timestamp with the uptime, and set
NEEDS_FSCK_CHECK=yes if it's older than the last reboot.
** Changed in: update-notifier (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/692355/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
