From owner-freebsd-hackers@FreeBSD.ORG  Sat Nov 26 11:25:57 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 D8229106564A
	for <hackers@freebsd.org>; Sat, 26 Nov 2011 11:25:57 +0000 (UTC)
	(envelope-from utisoft@gmail.com)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com
	[209.85.210.182])
	by mx1.freebsd.org (Postfix) with ESMTP id A36578FC0C
	for <hackers@freebsd.org>; Sat, 26 Nov 2011 11:25:57 +0000 (UTC)
Received: by iakl21 with SMTP id l21so9005605iak.13
	for <hackers@freebsd.org>; Sat, 26 Nov 2011 03:25:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:from:date
	:x-google-sender-auth:message-id:subject:to:cc:content-type;
	bh=2P3qLysTSr5KBar2TohbpS+lkcaJmNGzPk64KhNByk8=;
	b=rLMYbrtdwN5zXRynzjwRPb+3Cs8M/N42jg67pFqPtL02aWqqlOmKXYUQgfXVPne/pL
	J7IUKcayt5yV9Yc+xQ2VtxGPY6Z2+wAgWiD5IOUuJfOz4VWNolAO3YUKk2k5N0JJkuSY
	6hGNqjJDZkGprC7UaMyqeepDgEY8VXXnheXdM=
Received: by 10.42.29.1 with SMTP id p1mr11421865icc.40.1322304901379; Sat, 26
	Nov 2011 02:55:01 -0800 (PST)
MIME-Version: 1.0
Sender: utisoft@gmail.com
Received: by 10.231.12.139 with HTTP; Sat, 26 Nov 2011 02:54:29 -0800 (PST)
In-Reply-To: <4ED0944E.7020709@FreeBSD.org>
References: <201111260708.pAQ78wvO045883@slippy.cwsent.com>
	<4ED0944E.7020709@FreeBSD.org>
From: Chris Rees <crees@freebsd.org>
Date: Sat, 26 Nov 2011 10:54:29 +0000
X-Google-Sender-Auth: IjGyN7GWQidGYCKvQ16CUgOF9Gg
Message-ID: <CADLo83867HEyraqzS6+Pcyb=sTnVPP1MRZtiCVYvzcQJGDqZ-g@mail.gmail.com>
To: Doug Barton <dougb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Tom Evans <tevans.uk@googlemail.com>, 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: Sat, 26 Nov 2011 11:25:57 -0000

On 26 November 2011 07:25, Doug Barton <dougb@freebsd.org> wrote:
> On 11/25/2011 23:08, Cy Schubert wrote:
>> If average users really do need to run something at boot they're likely
>> running some kind of service
>
> I don't think second-guessing what users are doing is going to be a
> useful exercise here. I will also tell you flat out that this is not the
> only use for an @reboot cron job.
>
> Rather than debating whether users *should* be doing it this way or not,
> can we please focus on fixing it to be non-stupid?

+1

<hat class="armchair-general">
  I find the idea of using time since boot to decide whether this is
cron's first
  startup repellent in the extreme.  Whatever solution is decided (and
I'm thinking
  a variable passed to rc.d/cron or a state file in /var/run would
both work fine),
  PLEASE let's not go down the route of that.  How long? What if I need to
  restart cron shortly after boot? What if boot takes longer?
</hat>

Plenty of competent coders in here, but please consider me interested in helping
with a solution if needed.

Chris