Package: checksecurity
Version: 2.0.7-6
Severity: minor
Tags: patch
The only difference between /etc/cron.daily/checksecurity and
/etc/cron.weekly/checksecurity is that they run their payload with
arguments "daily" and "weekly" respectively. This means that
A) They both use the same lockfile: /var/lock/checksecurity.daily.
It's a pity this is necessary, but given that it is, the
shared lockfile should be simply /var/lock/checksecurity.
B) If they find that lockfile still in use, they emit the same error
message, "Unable to run /etc/cron.daily/checksecurity [...]
This probably means that the previous days instance is still
running". This would be a confusing message to receive when
this morning's run of check-diskfree has blocked this week's
run of check-setuid!
The patch below makes the verbiage less specific, to match the
current behaviour. (As a side benefit it eliminates the word
"days", with its missing apostrophe...)
--- /etc/cron.daily/checksecurity.old 2005-03-22 01:25:46.000000000 +0000
+++ /etc/cron.daily/checksecurity.new 2005-09-06 11:00:16.000000000 +0100
@@ -2,7 +2,7 @@
# /etc/cron.daily/checksecurity: Run the checksecurity script
# Steve Greenland <[EMAIL PROTECTED]>
-LOCKFILE=/var/lock/checksecurity.daily
+LOCKFILE=/var/lock/checksecurity
# The logfile we write our changes into.
LOGFILE=/var/log/checksecurity.log
@@ -26,8 +26,8 @@
cat <<EOF
Unable to run /etc/cron.daily/checksecurity because lockfile $LOCKFILE
-acquisition failed. This probably means that the previous days instance
-is still running. Please check and correct if necessary.
+acquisition failed. This probably means that a previous instance is
+still running. Please check and correct if necessary.
EOF
exit 1
--- /etc/cron.weekly/checksecurity.old 2005-03-22 01:25:46.000000000 +0000
+++ /etc/cron.weekly/checksecurity.new 2005-09-06 11:01:09.000000000 +0100
@@ -2,7 +2,7 @@
# /etc/cron.weekly/checksecurity: Run the checksecurity script
# Steve Greenland <[EMAIL PROTECTED]>
-LOCKFILE=/var/lock/checksecurity.daily
+LOCKFILE=/var/lock/checksecurity
# The logfile we write our changes into.
LOGFILE=/var/log/checksecurity.log
@@ -26,8 +26,8 @@
cat <<EOF
Unable to run /etc/cron.daily/checksecurity because lockfile $LOCKFILE
-acquisition failed. This probably means that the previous days instance
-is still running. Please check and correct if necessary.
+acquisition failed. This probably means that a previous instance is
+still running. Please check and correct if necessary.
EOF
exit 1
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.6.12.hurakan
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages checksecurity depends on:
ii cron 3.0pl1-86 management of regular background p
ii debconf 1.4.30.13 Debian configuration management sy
ii perl 5.8.4-8 Larry Wall's Practical Extraction
-- debconf information:
checksecurity/oldconf:
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
