PERIODIC.CONF(5) | MidnightBSD File Formats Manual | PERIODIC.CONF(5) |
periodic.conf
—
periodic job configuration information
The file periodic.conf
contains a
description of how daily, weekly and monthly system maintenance jobs should
run. It resides in the /etc/defaults directory and
parts may be overridden by a file of the same name in
/etc, which itself may be overridden by the
/etc/periodic.conf.local file.
The periodic.conf
file is actually sourced
as a shell script from each of the periodic scripts and is intended to
simply provide default configuration variables.
The following variables are used by periodic(8) itself:
For an unattended machine, suitable values for
daily_output, weekly_output,
and monthly_output might be
“/var/log/daily.log
”,
“/var/log/weekly.log
”, and
“/var/log/monthly.log
”
respectively, as
newsyslog(8) will
rotate these files (if they exists) at the appropriate times.
NO
”,
periodic(8) will mask
the script's output. If the return code of a script is ‘1’
and
⟨dir⟩_show_info
is set to “NO
”,
periodic(8) will mask
the script's output. If the return code of a script is ‘2’
and
⟨dir⟩_show_badconfig
is set to “NO
”,
periodic(8) will mask
the script's output. If these variables are set to neither
“YES
” nor
“NO
”, they default to
“YES
”,
“YES
” and
“NO
” respectively.
Refer to the periodic(8) manual page for how script return codes are interpreted.
The following variables are used by the standard scripts that reside in /etc/periodic/daily:
YES
” if you want to remove all
files matching daily_clean_disks_files daily.YES
”, this must also be set to the
number of days old that a file's access and modification times must be
before it is deleted.YES
” if you want the removed files
to be reported in your daily output.YES
” if you want to clear temporary
directories daily.YES
”.YES
”. Wild card characters are
permitted.YES
” if you want the removed files
to be reported in your daily output.YES
” if you wish to remove old
files from /var/preserve.YES
” if you want the removed files
to be reported in your daily output.YES
” if you wish old system
messages to be purged.YES
” if you wish old files in
/var/who to be purged.YES
” if you want the removed files
to be reported in your daily output.YES
” to run
sendmail
-bH
to
automatically purge stale entries from
sendmail(8)'s host
status cache. Files will be deleted using the same criteria as
sendmail(8) would
normally use when determining whether to believe the cached information,
as configured in /etc/mail/sendmail.cf.YES
” to create backup of EFI System
Partition (ESP).YES
” to create backup of gmirror
information (i.e., output of gmirror
list
), see
gmirror(8).YES
” to report a diff between the
new backup and the existing backup in the daily output.YES
” to create backups of partition
tables, and bootcode partition contents.YES
” to be verbose if existing
backups for kern.geom.conftxt or the partition tables differ from the new
backups.YES
” if you want the
/etc/master.passwd and
/etc/group files backed up and reported on.
Reporting consists of checking both files for modifications and running
chkgrp(8) on the
group file.YES
” if you want the
/etc/mail/aliases file backed up and modifications
to be displayed in your daily output.YES
” to create backup of the output
generated from the
zfs-list(8) and
zpool-list(8)
utilities.-v
.YES
” to create backup of the output
generated from the
zfs-get(8) and
zpool-get(8)
utilities.all
.all
.YES
” to report a diff between the
new backup and the existing backup in the daily output.YES
” if you want to run
calendar
-a
daily.YES
” if you want to rotate your
daily accounting files. No rotations are necessary unless
accounting_enable is enabled in
rc.conf(5).YES
” if you want your daily
accounting files to be compressed using
gzip(1).3
”.-s
) when
daily_accounting_enable is set to
“YES
”. The default is
-q
.YES
” if you want to run
/etc/news.expire.YES
” if you want to run
df(1) (with the arguments
supplied in daily_status_disks_df_flags) and
dump
-W
.YES
”. The default is
-l
-h
.YES
” if you want to run
zpool
status
on your
zfs(8) pools.YES
” if you want to run
zpool
list
on your
zfs(8) pools. Requires
daily_status_zfs_enable to be set to
YES
.YES
” if you want to run
gmirror
status
on your
gmirror(8)
devices.YES
” if you want to run
graid3
status
on your
graid3(8) devices.YES
” if you want to run
gstripe
status
on your
gstripe(8)
devices.YES
” if you want to run
gconcat
status
on your
gconcat(8)
devices.YES
” if you want to run
mfiutil
status
on your
mfi(4) devices.YES
” if you want to run
netstat
-i
.YES
”. The default is
-d
-W
.YES
” if you want to run
netstat(1) without the
-n
option (to do DNS lookups).YES
” if you want to run
uptime(1) (or
ruptime(1) if
rwhod_enable is set to
“YES
” in
/etc/rc.conf).YES
” if you want to run
mailq(1).YES
” if you want to shorten the
mailq(1) output when
daily_status_mailq_enable is set to
“YES
”.YES
” if you also want to run
mailq(1) on the submit
mail queue when daily_status_mailq_enable is set to
“YES
”. This may not work with MTAs
other than
sendmail(8).YES
” if you want to run the
security check. The security check is another set of
periodic(8) scripts.
The system defaults are in /etc/periodic/security.
Local scripts should be placed in
/usr/local/etc/periodic/security. See the
periodic(8) manual
page for more information.YES
” if you want the security check
output inline. The default is to either mail or log the output according
to the value of daily_status_security_output.NO
”. This variable behaves in the
same way as the *_output variables above, namely it
can be set either to one or more email addresses or to an absolute file
name.YES
” if you want to summarise mail
rejections logged to /var/log/maillog for the
previous day.YES
” if you want to enable NTP
status check.YES
” to check the running userland
and kernel are in sync.YES
” if you want to manually run
the mail queue at least once a day.YES
” if you also want to manually
run the submit mail queue at least once a day when
daily_queuerun_enable is set to
“YES
”.YES
” if you want to run a zfs scrub
periodically.The following variables are used by the standard scripts that reside in /etc/periodic/weekly:
YES
” if you want to run
/usr/libexec/locate.updatedb. This script is run
using nice
-5
as user
“nobody
”, and generates the table
used by the locate(1)
command.YES
” if you want to run
/usr/libexec/makewhatis.local. This script
regenerates the database used by the
apropos(1)
command.YES
” if you want to locate orphaned
files on the system. An orphaned file is one with an invalid owner or
group.YES
” if you want to use
pkg-version(8) to
list installed packages which are out of date.YES
”, this variable specifies the
program that is used to determine the out of date packages. If unset, the
pkg-version(8)
program is used. As an example, this variable might be set to
“portversion
” if the
ports/sysutils/portupgrade port has been
installed.Note, if the pkg_version variable is set
to “portversion
”, it will also be
necessary to arrange that the correct INDEX file
is specified using environment variables and that
pkg_version_index is cleared in
/etc/periodic.conf
(“pkg_version_index=
”).
The following variables are used by the standard scripts that reside in /etc/periodic/monthly:
YES
” if you want to do login
accounting using the ac(8)
command.The following variables are used by the standard scripts that reside in /etc/periodic/security. Those scripts are usually run from daily (daily_status_security_enable), weekly (weekly_status_security_enable), and monthly (monthly_status_security_enable) periodic hooks. The ..._period of each script can be configured as “daily”, “weekly”, “monthly” or “NO”. Note that when periodic security scripts are run from crontab(5), they will be always run unless their ..._enable or ..._period variable is set to “NO”.
-b
-u
.YES
” to compare the modes and
modification times of setuid executables with the previous day's
values.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to verify checksums of all
installed packages against the known checksums in
/var/db/pkg.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to check for files where the
group of a file has less permissions than the world at large. When users
are in more than 14 supplemental groups these negative permissions may not
be enforced via NFS shares.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to check for changes mounted
file systems to the previous day's values.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” if you want to ignore
amd(8) mounts when
comparing against yesterday's file system mounts in the
security_status_chkmounts_enable check.YES
” to check
/etc/master.passwd for accounts with UID 0.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to check
/etc/master.passwd for accounts with empty
passwords.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to check
/etc/login.conf ownership, see
login.conf(5) for
more information.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to show log entries for
packets denied by ipfw(8)
since yesterday's check.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to show log entries for
packets denied by ipf(8)
since yesterday's check.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to show log entries for
packets denied by pf(4)
since yesterday's check.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to display
ipfw(8) rules that have
reached their verbosity limit.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to show new
dmesg(8) entries since
yesterday's check.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to display failed logins from
/var/log/messages in the previous day.daily
”,
“weekly
”,
“monthly
” or
“NO
”.YES
” to display connections denied
by tcpwrappers (see
hosts_access(5))
from /var/log/messages during the previous
day.daily
”,
“weekly
”,
“monthly
” or
“NO
”.apropos(1), calendar(1), df(1), diff(1), gzip(1), locate(1), man(1), msgs(1), netstat(1), nice(1), login.conf(5), rc.conf(5), ac(8), chkgrp(8), dump(8), newsyslog(8), periodic(8), pkg-version(8), sendmail(8)
The periodic.conf
file appeared in
FreeBSD 4.1.
Brian Somers <brian@Awfulhak.org>
November 7, 2020 | midnightbsd-3.1 |