[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#892793: marked as done (stretch-pu: package cron/128+deb9u2)

Your message dated Sun, 2 Dec 2018 17:00:24 +0100
with message-id <20181202160024.GA20862@tomate.cristau.org>
and subject line Re: Bug#892793: stretch-pu: package cron/128+deb9u2
has caused the Debian Bug report #892793,
regarding stretch-pu: package cron/128+deb9u2
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 owner@bugs.debian.org
immediately.)


-- 
892793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892793
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: pu

 Fix bugs in cron that prevents it from working properly in environments
 where centralised user databases are used (e.g. LDAP, Windows AD).

 The changes introduce a dependency in the init.d file (for sssd) and in
 the service unit file to ensure that cron is started after these services
 are operative.

 Please review and, if possible, accept this version for stretch.

 Best regards


 Javier Fernandez-Sanguino





diff -u cron-3.0pl1/debian/changelog cron-3.0pl1/debian/changelog
--- cron-3.0pl1/debian/changelog
+++ cron-3.0pl1/debian/changelog
@@ -1,3 +1,17 @@
+cron (3.0pl1-128+deb9u2) stretch; urgency=medium
+
+  * debian/cron.init: Add sssd to the services that should be started/stopped
+    before/after cron
+  * debian/cron.service: Add a dependency on remote-fs.target (Closes: #815088)
+  * debian/cron.service: Add dependency on nss-user-lookup.target in the
+    definition which properly fixes the issues when cron is started
+    before centralised user repositories are available (e.g. LDAP
+    or Active Directory). This should avoid errors in syslog similar to
+    the following: "crond[PID]: (CRON) bad username (/etc/cron.d/JOBNAME)"
+    (Closes: #767016, #801384, #783665) (LP: #1593317)
+
+ -- Javier Fernández-Sanguino Peña <jfs@debian.org>  Sun, 11 Mar 2018 22:32:18 +0100
+
 cron (3.0pl1-128+deb9u1) stretch; urgency=medium
 
   * Non-maintainer upload.
diff -u cron-3.0pl1/debian/cron.init cron-3.0pl1/debian/cron.init
--- cron-3.0pl1/debian/cron.init
+++ cron-3.0pl1/debian/cron.init
@@ -5,8 +5,8 @@
 # Provides:          cron
 # Required-Start:    $remote_fs $syslog $time
 # Required-Stop:     $remote_fs $syslog $time
-# Should-Start:      $network $named slapd autofs ypbind nscd nslcd winbind
-# Should-Stop:       $network $named slapd autofs ypbind nscd nslcd winbind
+# Should-Start:      $network $named slapd autofs ypbind nscd nslcd winbind sssd
+# Should-Stop:       $network $named slapd autofs ypbind nscd nslcd winbind sssd
 # Default-Start:     2 3 4 5
 # Default-Stop:
 # Short-Description: Regular background program processing daemon
diff -u cron-3.0pl1/debian/cron.service cron-3.0pl1/debian/cron.service
--- cron-3.0pl1/debian/cron.service
+++ cron-3.0pl1/debian/cron.service
@@ -1,6 +1,7 @@
 [Unit]
 Description=Regular background program processing daemon
 Documentation=man:cron(8)
+After=remote-fs.target nss-user-lookup.target
 
 [Service]
 EnvironmentFile=-/etc/default/cron

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Mon, Apr 02, 2018 at 03:58:35PM +0200, Julien Cristau wrote:
> Control: tag -1 moreinfo
> 
> On Tue, Mar 13, 2018 at 00:43:45 +0100, Javier Fernández-Sanguino Peña wrote:
> 
> >  Fix bugs in cron that prevents it from working properly in environments
> >  where centralised user databases are used (e.g. LDAP, Windows AD).
> > 
> >  The changes introduce a dependency in the init.d file (for sssd) and in
> >  the service unit file to ensure that cron is started after these services
> >  are operative.
> > 
> >  Please review and, if possible, accept this version for stretch.
> > 
> Bug #815088 is not marked as fixed in unstable.  What is its status
> there?
> 
Still no change, closing.  Feel free to make a new request once this
issue is fixed in sid.

Cheers,
Julien

--- End Message ---
Reply to: