weekly periodic security status

Darren Pilgrim list_freebsd at bluerosetech.com
Mon Aug 26 16:30:15 UTC 2013


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.


More information about the freebsd-hackers mailing list