FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=master 2018-08-11T17:11:08Z 2018-08-11T17:11:08Z Brad Davis brd@FreeBSD.org 2018-08-11T17:11:08Z urn:sha1:81ea85a8845662ca329a954eeeb3e6d4124282a2 This makes pkgbase easier by tagging these as CONFS so they are properly tagged as config files. Approved by: will (mentor) Sponsored by: Essen Hackathon Differential Revision: https://reviews.freebsd.org/D16553 2017-04-06T01:37:03Z Alan Somers asomers@FreeBSD.org 2017-04-06T01:37:03Z urn:sha1:e2a212c1fbbe4b9a54dc7893b0cd363da5e3b319 Previously, 450.status-security would always set rc=3 in inline mode, because it doesn't know whether "periodic security" is going to find anything interesting. But this annoyingly results in daily reports that simply say "Security check: \n\n-- End of daily output --". This change fixes that by testing whether "periodic security" printed anything, and setting 450.status-security's exit status to 3 if it did. An alternative would be to change the exit status of periodic(8) to be the worst of its scripts' exit statuses, but that would be a more intrusive change. Reviewed by: brian MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D10267 2017-02-01T23:22:54Z Alan Somers asomers@FreeBSD.org 2017-02-01T23:22:54Z urn:sha1:cb23468e75163477cf6b9ba2624f2078339a15d1 If one of the scripts listed in (daily|weekly|monthly)_local is executable, 999.local should simply execute it. Only if the script isn't executable should 999.local assume it needs /bin/sh. Reviewed by: brian MFC after: 3 weeks Sponsored by: Spectra Logic Corp 2016-01-28T18:44:31Z Glen Barber gjb@FreeBSD.org 2016-01-28T18:44:31Z urn:sha1:a5a71822df59f065eed64423dfc83cc9446e76c8 Add periodic(8) accounting scripts to acct package. Sponsored by: The FreeBSD Foundation 2014-05-06T04:22:01Z Warner Losh imp@FreeBSD.org 2014-05-06T04:22:01Z urn:sha1:c6063d0da8e1f8d8452b0c2ee1c7ad718c1a7052 from the latter. 2013-08-27T22:37:29Z Jung-uk Kim jkim@FreeBSD.org 2013-08-27T22:37:29Z urn:sha1:b81c4e6563f547d0446a059567ec89f1db0e52e3 2013-08-27T21:28:12Z Jeremie Le Hen jlh@FreeBSD.org 2013-08-27T21:28:12Z urn:sha1:622ceeb3fb8d2456a6d2411eaf887347237a6256 2013-08-27T21:20:28Z Jeremie Le Hen jlh@FreeBSD.org 2013-08-27T21:20:28Z urn:sha1:69b55c23cb93350a21cd39c317881cda0b9187ca 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@ 2011-06-17T21:30:21Z Ed Schouten ed@FreeBSD.org 2011-06-17T21:30:21Z urn:sha1:9f0c9022c2a001dc3c2983af781a73d31360af12 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. 2011-06-17T20:47:44Z Ed Schouten ed@FreeBSD.org 2011-06-17T20:47:44Z urn:sha1:f1c344b293cfcba047eb18904e3fa7d0d554dd9a 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.