On 8/25/13 7:05 PM, 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):
security_status_chksetuid_enable=daily
On 23/08/2013 15:23, Dmitry Sivachenko wrote:
Hello!
I am using FreeBSD-9-STABLE on the following hardware:
FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 SMT threads
So I have 2 physical CPUs with 6 core each.
# cpuset -g
pid -1 mask:
On Sun, 25 Aug 2013 22:03:58 +0200
Jeremie Le Hen wrote:
I've implemented it here:
http://people.freebsd.org/~jlh/security_status_period.diff
Doesn't this mean that if you want to run periodic security from
crontab or manually etc, you have to override every single entry to
crontab in
On Mon, Aug 26, 2013 at 05:03:32PM +0100, RW wrote:
On Sun, 25 Aug 2013 22:03:58 +0200
Jeremie Le Hen wrote:
I've implemented it here:
http://people.freebsd.org/~jlh/security_status_period.diff
Doesn't this mean that if you want to run periodic security from
crontab or manually etc,
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,
Darren
On Mon, Aug 26, 2013 at 12:29:30PM -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
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
7 matches
Mail list logo
