Bug 155417 - changing startup setttings for seccheck
Summary: changing startup setttings for seccheck
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Security (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Thomas Biege
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-06 14:59 UTC by Christian Andretzky
Modified: 2006-07-31 12:56 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Andretzky 2006-03-06 14:59:08 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
Comment 1 Thomas Biege 2006-07-31 12:56:50 UTC
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.