Date: Sat, 26 Nov 2011 14:53:05 -0500 From: Jason Hellenthal <jhell@DataIX.net> To: Dieter BSD <dieterbsd@engineer.com> Cc: hackers@freebsd.org Subject: Re: cron(8) mis-feature with @reboot long after system startup Message-ID: <20111126195305.GC2368@DataIX.net> In-Reply-To: <20111125175344.233450@gmx.com> References: <20111125175344.233450@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--H8ygTp4AXg6deix2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 25, 2011 at 12:53:43PM -0500, Dieter BSD wrote:
> The system doesn't go multiuser until the rc jobs complete,
> even if you attempt to background them with '&'. ??This can be
> a problem with long running jobs. ??I started using cron @reboot
> for this reason.
>=20
> I haven't run into the problem since I've never needed to run
> /etc/rc.d/cron restart.
Yeah I have never ran into this either throughout all my use cases. cron(8)=
has always ran and stayed running until my OP where I found out the hardwa=
y. Would make someone proud to be called Paul Vixie. ;)
>=20
> > Add an option to cron to check lastlog and if within 5 or 10 minutes
> > of the last reboot, then call run_reboot_jobs().
>=20
> Depending on timestamps might be okay as a temporary quick-and-dirty
> workaround, but there is likely to be a case where it will also do the
> wrong thing. ??What if you need to restart cron within the 5-10 minutes?
>=20
> Maybe something like: rc script sets a flag, cron_reboot script checks
> and resets flag. ??The flag could be a file ("> /tmp/rebooting_system").
> Better yet, a run-the-reboot-script command line option could be added
> to cron.
cron(8) already creates a pid file. Maybe it wouldn't be so bad to just che=
ck the timestamp of that before creating its new pid file along with compar=
ing to system boottime so we could make an accurate measure whether it shou=
ld or should not run the @reboot extension at least down to 1 minute.
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
--H8ygTp4AXg6deix2
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJO0UOhAAoJEJBXh4mJ2FR+GREH+wVcZUtj8FjknGLpY1IzO6QF
BDOC5X1dDtxka0TnUdvCcvmGfFM7lx4AqTnRKljfUeEMfRuDA8myrdv7pAUEbNSp
wERAKFRG3zm8cUw7Mh2KZNc+9VD0rQjmo6KVtsqgByx8KfvPbY5EriZN2gaFkgf7
mwjg1dEdWOAMC75V16c2T1UeIUaM4AtfdeZxi1Br67Oi3bwmuR+8T/Z82hxZ/Lbo
ss7gqV9WpACZK7JbZeTJvS9V3oQGk5VyH618KfJn6aewuYo2Smn6Zb9VBD1iDP9u
0iafQBEcvYtxzALodv+iuZPwPR9hcR8JtgetKqybBvmZXGM9gUi+YqoRMBZYsr4=
=0R4k
-----END PGP SIGNATURE-----
--H8ygTp4AXg6deix2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111126195305.GC2368>