From owner-freebsd-hackers@FreeBSD.ORG  Fri Nov 25 08:29:52 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 39BB9106564A
	for <hackers@FreeBSD.org>; Fri, 25 Nov 2011 08:29:52 +0000 (UTC)
	(envelope-from stb@lassitu.de)
Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea])
	by mx1.freebsd.org (Postfix) with ESMTP id 0357F8FC1B
	for <hackers@FreeBSD.org>; Fri, 25 Nov 2011 08:29:52 +0000 (UTC)
Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id DCB16102509;
	Fri, 25 Nov 2011 09:29:50 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Stefan Bethke <stb@lassitu.de>
In-Reply-To: <20111125070241.GA7915@DataIX.net>
Date: Fri, 25 Nov 2011 09:29:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <166BF54D-CEA6-49F5-B8A0-14A647F94766@lassitu.de>
References: <20111125070241.GA7915@DataIX.net>
To: Jason Hellenthal <jhell@DataIX.net>
X-Mailer: Apple Mail (2.1251.1)
Cc: 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 08:29:52 -0000

Am 25.11.2011 um 08:02 schrieb Jason Hellenthal:

> 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.
>=20
> So with that said... is there a way we could actually make this run =
@reboot only ?

I didn't even know cron had this feature.  Why wouldn't you add custom =
rc.d scripts for these tasks, or add the commands to rc.local?


Stefan

--=20
Stefan Bethke <stb@lassitu.de>   Fon +49 151 14070811