Hello Christian, thanks for your very fast reply. On Sun, Jul 24, 2011 at 08:42:04PM +0200, Christian Kastner wrote: > On 07/24/2011 04:46 PM, Helge Kreutzmann wrote: > > In a freshly installed wheezy systems, @reboot jobs are not run. > > > > Jul 24 18:04:51 sneo /usr/sbin/cron[2252]: (CRON) INFO (pidfile fd = 3) > > Jul 24 18:04:51 sneo /usr/sbin/cron[2253]: (CRON) STARTUP (fork ok) > > Jul 24 18:04:51 sneo /usr/sbin/cron[2253]: (CRON) INFO (Skipping @reboot > > jobs -- not system startup) > > Jul 24 18:09:50 sneo anacron[2178]: Job `cron.daily' started > > Jul 24 18:09:50 sneo anacron[2933]: Updated timestamp for job `cron.daily' > > to 2011-07-24 > > > > (Please note this is done at every reboot, and yes, it *is* system startup). > > 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.
> it doesn't, it runs @reboot jobs, then creates it (so they are skipped
> next time). cron does this to ensure @reboot jobs are really run only
> once, instead of eg: when cron is restarted for some reason.
Thanks for the explanation.
> 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?
Thanks!
Greetings
Helge
--
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
