summaryrefslogtreecommitdiffstats
path: root/etc/periodic/monthly
Commit message (Collapse)AuthorAgeFilesLines
* Fix a typo introduced in r254975.jkim2013-08-271-1/+1
|
* Install 450.status-security.jlh2013-08-271-1/+2
|
* Make the period of each periodic security script configurable.jlh2013-08-271-0/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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@
* Add WITHOUT_UTMPX switch to the build system.ed2011-06-171-2/+7
| | | | | | | | | This knob removes the tools that are exclusively used to view and maintain the databases maintained by utmpx, namely last, users, who, wtmpcvt, ac, lastlogin and utxrm. The tool w is not in this list, because it has some other functionality which is unrelated to utmpx; it is hardlinked to the uptime tool.
* Don't omit ac(8) as part of WITHOUT_ACCT.ed2011-06-171-7/+2
| | | | | | | The WITHOUT_ACCT switch is supposed to omit tools related to process accounting, namely accton and sa. ac(8) is just a simple tool that prints statistics based on data in the utx.log database. It has nothing to do with the former.
* Let rc and periodic infrastructure and newsyslog use the utmpx files.ed2010-01-131-1/+1
|
* add new build knobs and jigger some existing controls to improvesam2008-09-211-2/+9
| | | | | | | | 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
* Make it work with POSIX sort (POS arg).ache2002-09-241-1/+1
| | | | All old sorts understand -k too.
* Install scripts via FILES (purposedly not via SCRIPTS that wouldru2002-07-181-1/+1
| | | | strip the suffixes).
* Temporarily change our umask to 066 so that the potential creationbrian2002-05-171-0/+3
| | | | | | | | | | of wtmp.0 is done as mode 600. This ensures that tight permissions set in /etc/newsyslog.conf for wtmp logging aren't ``betrayed''. Suggested by: lumpy <lumpy@the.whole.net> MFC after: 3 days
* Handle .bz2 files created by newsyslogbrian2002-04-301-0/+4
| | | | | | PR: 37529 Partially submitted by: Peter Hollaubek <fifteen@inext.hu> MFC after: 1 week
* Handle wtmp.0 being compressedbrian2001-11-201-5/+16
| | | | | | PR: 32113 Submitted by: Yar Tikhiy <yar@comp.chem.msu.su> MFC after: 1 week
* Small adjustment to whitespace in outputdougb2001-06-011-1/+1
|
* Another overhaul of the periodic stuff.brian2000-09-142-8/+23
| | | | | | | | | | | | | | | 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
* Introduce /etc/defaults/periodic.conf, similar in concept to rc.conf.brian2000-06-232-10/+39
| | | | | | | 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
* $Id$ -> $FreeBSD$peter1999-08-273-3/+3
|
* Now that newsyslog is capable of doing this at a specific time,wollman1999-01-281-12/+3
| | | | | | | let it rotate /var/log/wtmp again, and update monthly/200.accounting to take this into account. (Some sites might want to change the parameters of the rotation; it's easier to do this when it's all centralized in newsyslog.conf.)
* PR: 1708, 5448danny1998-02-091-5/+17
| | | | | Reviewed by: Alex Nash, Steve Price Enhance wtmp monthly handling
* Copy /etc/cron.d to /etc/periodic per-request of many.pst1997-08-163-0/+27
This wasn't done with a repository copy because there was no history of any consequence. Flames to me.
OpenPOWER on IntegriCloud