From owner-freebsd-hackers@FreeBSD.ORG  Tue Aug 27 21:32:48 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 0505E5DA
 for <freebsd-hackers@freebsd.org>; Tue, 27 Aug 2013 21:32:48 +0000 (UTC)
 (envelope-from jlh@FreeBSD.org)
Received: from caravan.chchile.org (caravan.chchile.org [178.32.125.136])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id BDF3D2427
 for <freebsd-hackers@freebsd.org>; Tue, 27 Aug 2013 21:32:47 +0000 (UTC)
Received: by caravan.chchile.org (Postfix, from userid 1000)
 id 74096C0E5E; Tue, 27 Aug 2013 21:32:46 +0000 (UTC)
Date: Tue, 27 Aug 2013 23:32:46 +0200
From: Jeremie Le Hen <jlh@FreeBSD.org>
To: Darren Pilgrim <list_freebsd@bluerosetech.com>
Subject: Re: weekly periodic security status
Message-ID: <20130827213246.GS24767@caravan.chchile.org>
Mail-Followup-To: Darren Pilgrim <list_freebsd@bluerosetech.com>,
 FreeBSD Hackers <freebsd-hackers@freebsd.org>
References: <20130822204958.GC24767@caravan.chchile.org>
 <5217AD9E.1000100@bluerosetech.com>
 <CA+E3k910-BqOdDtA9sWTxVuKxtJSS02w4PSeTmM+JxPqNQ5Jyw@mail.gmail.com>
 <20130824165704.GD24767@caravan.chchile.org>
 <20130825110520.GJ24767@caravan.chchile.org>
 <521A34A2.303@bluerosetech.com>
 <20130825173715.GK24767@caravan.chchile.org>
 <521B826A.6020402@bluerosetech.com>
 <20130826210906.GO24767@caravan.chchile.org>
 <521BD278.80007@bluerosetech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <521BD278.80007@bluerosetech.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Tue, 27 Aug 2013 21:32:48 -0000

Hi Darren,

On Mon, Aug 26, 2013 at 06:11:04PM -0400, Darren Pilgrim wrote:
> On 8/26/2013 5:09 PM, Jeremie Le Hen wrote:
> > On Mon, Aug 26, 2013 at 12:29:30PM -0400, Darren Pilgrim wrote:
> >> The new framework would let me rely on the environment instead of $0,
> >> which, IMO, is more reliable.  I'd need to be able to tell periodic to
> >> run that script with the daily, weekly and monthly security runs, though.
> >
> > If I understand what you say correctly, this should continue to work.
> 
> As I understand the framework, I can only set the enable to "NO", 
> "daily", "weekly" or "monthly".  Periodic will only run it one of the 
> periods.  How would I set it to run in all three?  How would I set to 
> run in only two of the three periods?
> 
> It seems like you could add this functionality by adding stars to each 
> end of the case patterns in check_yesno_period.

I've committed my work.  Can you propose me a patch implementing what
you request please?

Thanks,
-- 
Jeremie Le Hen

Scientists say the world is made up of Protons, Neutrons and Electrons.
They forgot to mention Morons.