From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 26 16:30:15 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4055FFC8; Mon, 26 Aug 2013 16:30:15 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com [IPv6:2607:f2f8:a450::66]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 262AA2F3A; Mon, 26 Aug 2013 16:30:15 +0000 (UTC) Received: from chombo.houseloki.net (c-76-27-220-79.hsd1.wa.comcast.net [76.27.220.79]) by yoshi.bluerosetech.com (Postfix) with ESMTPSA id 0851DE6001; Mon, 26 Aug 2013 09:30:06 -0700 (PDT) Received: from [192.168.1.102] (static-71-242-248-73.phlapa.east.verizon.net [71.242.248.73]) by chombo.houseloki.net (Postfix) with ESMTPSA id 86F1CE4F; Mon, 26 Aug 2013 09:29:33 -0700 (PDT) Message-ID: <521B826A.6020402@bluerosetech.com> Date: Mon, 26 Aug 2013 12:29:30 -0400 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jeremie Le Hen Subject: Re: weekly periodic security status References: <20130822204958.GC24767@caravan.chchile.org> <5217AD9E.1000100@bluerosetech.com> <20130824165704.GD24767@caravan.chchile.org> <20130825110520.GJ24767@caravan.chchile.org> <521A34A2.303@bluerosetech.com> <20130825173715.GK24767@caravan.chchile.org> In-Reply-To: <20130825173715.GK24767@caravan.chchile.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2013 16:30:15 -0000 On 8/25/2013 1:37 PM, Jeremie Le Hen wrote: > Hi Darren, > > On Sun, Aug 25, 2013 at 12:45:22PM -0400, Darren Pilgrim wrote: >> On 8/25/2013 7:05 AM, Jeremie Le Hen wrote: >>> And the following variables to control whether you want each check to >>> run "daily", "weekly" or directly from "crontab" (the default, backward >>> compatible values are shown): >> >> What do we do if we want to run a check both daily and weekly? > > I really don't see the point of running some checks weekly when you do > daily. Do you have a particular example in mind? On one set of systems, I have a log analyser run as a periodic script. On a daily run, it grabs and filters logs into a database. On weekly runs, it does some statistical analysis of the filtered logs in the database. On monthly runs, it does a larger set of stats and a bit of housekeeping. The script lives in /usr/local/libexec and is hardlinked into the /usr/local/etc/periodic/ subtree and cases out the value of $0. 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.