Date: Fri, 25 Nov 2011 02:02:41 -0500 From: Jason Hellenthal <jhell@DataIX.net> To: hackers@FreeBSD.org Subject: cron(8) mis-feature with @reboot long after system startup Message-ID: <20111125070241.GA7915@DataIX.net>
next in thread | raw e-mail | index | archive | help
--cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List, When using @reboot with cron you expect your proccesses to always start when the system boots up and only when the system boots. But long after the system in question had been booted, my @reboot processes ran again! after a (/etc/rc.d/cron restart). This is normally fine and dandy until one of your @reboot jobs needs to contain a process that purges files "files that are already in use by a running daemon since the system has not rebooted" and becomes hazardous. So with that said... is there a way we could actually make this run @reboot only ? Compare the system boottime (kern.boottime) to the current time and if it is greater than ?5 minutes? do not run on any @reboot's ? or add yet another extension @boottime so it does not throw off current functionality ? Surely I could modify the scripts which do this but I find it unproductive and counter intuitive for the need to explain that @reboot means "When cron is restarted" even though the name means something completely opposite. Regards & Happy Thanks Giving. --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJOzz2QAAoJEJBXh4mJ2FR+jo4H/0pJ5OFg7JsUbu2hMw5tm5xE yLt2eMIiPiaM2PEOTBA1eo0iMF48U2BQhA5DIkAWEwO3zIMrj/HjVbOW7NT83Y7z 5MLjIWZGZmaWqlE7chlFpnQNAgLwtnzr9AljXggs9j7WH9uPYkNOoZc7Ybm0lwSe 6qEPaLc1F/IYw7FNyuOJlkjmAydDY0BBks4NyzlQB1lLAAmC2cijelpJWK3XwNmx NfOgHxCscW7C1ZDLGwCzKKHWhl6ibF+HJ/yeOCYwBs+N+p3yXQmTfzoXzxq7+Idb 3jHNsx4YZkkmyM/2/6vxPajpJxPwc+C5PcX7F2YsIx4ixxzTtzUWLrL2GLr7hTk= =P9LA -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111125070241.GA7915>