Your message dated Sun, 8 May 2022 16:43:08 +0200
with message-id <YnfW/[email protected]>
and subject line bugs homekeeping
has caused the Debian Bug report #634215,
regarding Having init.d/cron run early breaks the semantics of @reboot time
specification
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
634215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634215
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-118
Severity: normal
Tags: patch
init.d/cron used to be one of the last scripts to run. With
parallel boot sequence, this is not necessarily true. In order
to preserve the semantics of the @reboot time specification, I
suggest to:
--- cron 2011-07-17 21:04:04.000000000 +0300
+++ cron.new 2011-07-17 21:04:34.000000000 +0300
@@ -3,7 +3,7 @@
#
### BEGIN INIT INFO
# Provides: cron
-# Required-Start: $remote_fs $syslog $time
+# Required-Start: $remote_fs $syslog $time $all
# Required-Stop: $remote_fs $syslog $time
# Should-Start: $network $named slapd autofs ypbind nscd nslcd
# Should-Stop: $network $named slapd autofs ypbind nscd nslcd
As an aside, I do not understand why one should list
$remote_fs $syslog $time
when $all is stated. I mean, doesn't $all includes those services?
Having $all listed with other services is copied from init.d/rc.local.
Can it be that $all is insserv's specific, and there was an attempt
to allow other boot scripts' enumerating facilities?
--- End Message ---
--- Begin Message ---
Hello, this bug report is 13 years old and has received no information
for this long time.
Either it is still useful or not. Many changes have occured since the
publication of this bug, some have touched deep features of cron, and
many people have lived their life with debian's cron without activating
this bug report again.
Please check whether this bug should reopened currently. I shall close it
now.
Best regards, Georges.
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: PGP signature
--- End Message ---
