| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
from the latter.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are now six additional variables
weekly_status_security_enable
weekly_status_security_inline
weekly_status_security_output
monthly_status_security_enable
monthly_status_security_inline
monthly_status_security_output
alongside their existing daily counterparts. They all have the same
default values.
All other "daily_status_security_${scriptname}_${whatever}"
variables have been renamed to "security_status_${name}_${whatever}".
A compatibility shim has been introduced for the old variable names,
which we will be able to remove in 11.0-RELEASE.
"security_status_${name}_enable" is still a boolean but a new
"security_status_${name}_period" allows to define the period of
each script. The value is one of "daily" (the default for backward
compatibility), "weekly", "monthly" and "NO".
Note that when the security periodic scripts are run directly from
crontab(5) (as opposed to being called by daily or weekly periodic
scripts), they will run unless the test is explicitely disabled with a
"NO", either for in the "_enable" or the "_period" variable.
When the security output is not inlined, the mail subject has been
changed from "$host $arg run output" to "$host $arg $period run output".
For instance:
myfbsd security run output -> myfbsd security daily run output
I don't think this is considered as a stable API, but feel free to
correct me if I'm wrong.
Finally, I will rearrange periodic.conf(5) and default/periodic.conf
to put the security options in their own section. I left them in
place for this commit to make reviewing easier.
Reviewed by: hackers@
|
| |
|
|
|
|
|
|
|
|
|
| |
utilities and related support files for manual pages, which were previously
controlled by MAN. For POLA, the default depends on MAN, i.e., WITHOUT_MAN
implies WITHOUT_MAN_UTILS and WITH_MAN implies WITH_MAN_UTILS. This patch
is slightly improved by me from:
PR: misc/145212
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
control over the result of buildworld and installworld; this especially
helps packaging systems such as nanobsd
Reviewed by: various (posted to arch)
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
of the depricated one.
PR: conf/108611
Submitted by: TAOKA Fumiyoshi <fmysh at iijmio-mail dot jp>
Approved by: imp (mentor)
|
| |
|
|
|
|
|
| |
PR: conf/35242
Submitted by: Annihilator <annihilator.c@usa.net>
|
|
|
|
|
|
|
| |
This is particularly convenient on a cluster of machines to prevent
having to rebuild the INDEX file on each.
Reviewed by: portmgr
|
|
|
|
| |
of pkg_version in periodic/weekly/400.status-pkg.
|
|
|
|
| |
strip the suffixes).
|
|
|
|
|
| |
PR: bin/35558
Submitted by: Nicolas Rachinsky <list@rachinsky.de>
|
| |
|
|
|
|
|
| |
PR: 27707
Approved by: bmah, markm
|
| |
|
| |
|
|
|
|
| |
to perl5 modules installed by hand.
|
| |
|
|
|
|
| |
LC_ALL takes precedence over other LC_* envariables.
|
|
|
|
| |
in their name.
|
| |
|
|
|
|
|
|
|
|
| |
from being installed, and make rmail conditional on neither of
NO_SENDMAIL and NOUUCP.
PR: bin/21321
Submitted by: Me
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All periodic sub-scripts <larf> now have their return codes interpreted
by periodic(8). Output may be masked based on variable values in
periodic.conf.
It's also now possible to email periodic output to arbitrary addresses,
or to send it to a log file, examples of which can be found in
newsyslog.conf.
The upshot of it all should be no discernable changes to the default
behaviour of periodic(8).
PR: 21250
|
|
|
|
| |
Forgotten by: brian
|
| |
|
|
|
|
|
|
|
| |
The only change in the default functionality should be that
the output reports are slightly more verbose WRT files deleted.
Not objected to by: freebsd-arch
|
| |
|
|
|
|
| |
Submitted by: "Alexey Zelkin" <phantom@crimea.edu>
|
| |
|
|
|
|
|
|
|
| |
home directory.
PR: 10700
Submitted by: Sergey Korsak <skif@1plus1.net>
|
|
|
|
|
| |
used to cleanup old files, and replace it by -delete which has been
present in our find(1) for ages now.
|
|
|
|
|
|
|
| |
using one of two hard-coded values.
PR: 5365
Submitted by: Ruslan Shevchenko <rssh@cam.grad.kiev.ua>
|
|
|
|
|
| |
plain sysctl]. We already assumed that many standard commands
exist, and sysctl is not special.
|
|
|
|
| |
Do not run by default.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Philippe Charnier <charnier@xp11.frmug.org>
|
|
|
|
| |
an example, it's totally bogus.
|
|
This wasn't done with a repository copy because there was no
history of any consequence. Flames to me.
|