Bugzilla – Bug 155417
changing startup setttings for seccheck
Last modified: 2006-07-31 12:56:50 UTC
In the moment the secchk package is started via cron from a separate crontab /etc/cron.d/seccheck. This works only on machines which are running during the night. Missed secheck runs are not maked up. I would suggest to include the secheck runs instead of /etc/cron.d/ in the /etc/cron.{daily|weekly|monthly} structure. In this case missed secheck runs are executed if the {daily|weekly|monthly} jobs are executed. I'll append a simple script which does the job. It is stored in /etc/cron.daily and symlinked (with different names to make sure that daily|weekly|monthly jobs can run at the same time.) #!/bin/bash StartDir=$(dirname $0) if [ $StartDir == "." ]; then StartDir=$(pwd) fi DirName=${StartDir##*/} Time_Ext=${DirName##cron.} test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh $Time_Ext ./cron.daily/seccheck ./cron.monthly/seccheck.monthly -> ../cron.daily/seccheck ./cron.weekly/seccheck.weekly -> ../cron.daily/seccheck
We had this discussion in the past... * Tue Apr 24 2001 - garloff@suse.de - Move it back to cron.d/seccheck. Otherwise users who use their machine only occasionally would see a significant performance hit.