On 07/24/2011 09:38 PM, Helge Kreutzmann wrote: > On Sun, Jul 24, 2011 at 08:42:04PM +0200, Christian Kastner wrote: >> cron decides on whether to run @reboot jobs by checking if the file >> /var/run/crond.reboot exists. If it exists, cron skips @reboot jobs; if > > root@sneo:~# ls -l /var/run/crond.reboot > ---------- 1 root root 0 9. Jul 13:36 /var/run/crond.reboot > > Clearly looks like it has not been removed. > >> In your case, the /var/run/crond.reboot seems to be preserved across >> reboots, which I cannot reproduce. Could you post the output of >> `mount | grep run` here? > > tmpfs on /var/run/lock type tmpfs > (rw,noexec,nosuid,nodev,size=5242880,mode=1777,size=5242880,mode=1777) > tmpfs on /var/run/shm type tmpfs > (rw,nosuid,nodev,size=20%,mode=1777,size=20%,mode=1777) > tmpfs on /var/run type tmpfs > (rw,noexec,nosuid,relatime,size=818528k,mode=755) > > Shouldn't a tmpfs be empty after a reboot?
Definitely yes. /var/run/crond.reboot still being there would indicate that there's another FS in play, but I wouldn't really know why this is happening. One possibility would be that something went wrong during the recent /var/run -> /run transition (I see the above mounts under /run) Could you look into /etc/fstab (and maybe /etc/default/tmpfs) and see if you can spot something fishy? Christian
signature.asc
Description: OpenPGP digital signature
