From owner-freebsd-hackers@FreeBSD.ORG  Fri Nov 25 22:08:06 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: hackers@FreeBSD.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id D502B106564A
	for <hackers@FreeBSD.org>; Fri, 25 Nov 2011 22:08:06 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 8101114F638;
	Fri, 25 Nov 2011 22:08:06 +0000 (UTC)
Message-ID: <4ED011C6.8060605@FreeBSD.org>
Date: Fri, 25 Nov 2011 14:08:06 -0800
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:8.0) Gecko/20111110 Thunderbird/8.0
MIME-Version: 1.0
To: Cy Schubert <Cy.Schubert@komquats.com>
References: <201111251609.pAPG97dT008848@slippy.cwsent.com>
In-Reply-To: <201111251609.pAPG97dT008848@slippy.cwsent.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Jason Hellenthal <jhell@DataIX.net>, hackers@FreeBSD.org
Subject: Re: cron(8) mis-feature with @reboot long after system startup
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Nov 2011 22:08:06 -0000

On 11/25/2011 08:09, Cy Schubert wrote:
> You're right. Sorry. It was late, after a long night of O/T.

Actually I was in the same boat, which is why my reply was even grumpier
than usual, sorry.

Meanwhile I like your suggestion of having cron check that it's within
$time_period before running the @reboot jobs. I'm not quite so sure that
the current behavior needs to be preserved though ... I doubt people
purposely restart cron often enough to be anything but surprised  by the
current behavior.


Doug

-- 

		"We could put the whole Internet into a book."
		"Too practical."

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/