Bug#783665: marked as done (cron does not execute some non-root cron.d jobs when started before ypbind)
Your message dated Mon, 12 Mar 2018 23:49:37 + with message-idand subject line Bug#783665: fixed in cron 3.0pl1-130 has caused the Debian Bug report #783665, regarding cron does not execute some non-root cron.d jobs when started before ypbind 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 ow...@bugs.debian.org immediately.) -- 783665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cron Version: 3.0pl1-127 Severity: important Dear Maintainer, I have a file in /etc/cron.d that runs jobs as a user that is not in /etc/passwd, but is in my NIS passwd database. When I reboot the system the job never runs, and there is no error message in the logs. Other jobs in /etc/cron.d that have entries in /etc/passwd work fine. If I stop and start cron using systemctl the job with the user that is not in /etc/passwd but is in the NIS passwd database runs as scheduled. I believe this is a problem with the start up order for cron. On my system cron is starting up before ypbind. I think it should be starting up afterwards. I am not enough of an expert in systemd to figure out how to set up dependencies for cron to fix this. -- Package-specific info: --- EDITOR: not set --- /usr/bin/editor: /usr/bin/vim.gnome --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 36008 Oct 25 2014 /usr/bin/crontab --- /var/spool/cron: drwxr-xr-x 5 root root 48 Aug 29 2007 /var/spool/cron --- /var/spool/cron/crontabs: drwx-wx--T 2 root crontab 29 Apr 28 13:54 /var/spool/cron/crontabs --- /etc/cron.d: drwxr-xr-x 2 root root 105 Apr 26 14:51 /etc/cron.d --- /etc/cron.daily: drwxr-xr-x 2 root root 4096 Apr 28 11:39 /etc/cron.daily --- /etc/cron.hourly: drwxr-xr-x 2 root root 25 Apr 26 12:47 /etc/cron.hourly --- /etc/cron.monthly: drwxr-xr-x 2 root root 84 Apr 26 14:35 /etc/cron.monthly --- /etc/cron.weekly: drwxr-xr-x 2 root root 90 Apr 26 14:35 /etc/cron.weekly -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages cron depends on: ii adduser 3.113+nmu3 ii debianutils 4.4+b1 ii dpkg 1.17.25 ii init-system-helpers 1.22 ii libc62.19-18 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii lsb-base 4.1+Debian13+nmu1 Versions of packages cron recommends: ii sendmail-bin [mail-transport-agent] 8.14.4-8 Versions of packages cron suggests: ii anacron2.3-23 pn checksecurity ii logrotate 3.8.7-1+b1 Versions of packages cron is related to: pn libnss-ldap pn libnss-ldapd pn libpam-ldap pn libpam-mount ii nis 3.17-33 ii nscd 2.19-18 -- no debconf information --- End Message --- --- Begin Message --- Source: cron Source-Version: 3.0pl1-130 We believe that the bug you reported is fixed in the latest version of cron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated cron package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Mar 2018 22:00:01 +0100 Source: cron Binary: cron Architecture: source i386 Version: 3.0pl1-130 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Description: cron - process scheduling daemon Closes: 705570 757191 767016 783665 792572 801384 834728 840601 892720 892721 892724 Changes: cron (3.0pl1-130) unstable; urgency=medium . * debian/postinst: Do not do check if /var/spool/cron/crontabs if empty (Closes: 892720, 892721, 892724) * debian/cron.service: -
Bug#783665: marked as done (cron does not execute some non-root cron.d jobs when started before ypbind)
Your message dated Sun, 11 Mar 2018 23:04:21 + with message-idand subject line Bug#783665: fixed in cron 3.0pl1-129 has caused the Debian Bug report #783665, regarding cron does not execute some non-root cron.d jobs when started before ypbind 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 ow...@bugs.debian.org immediately.) -- 783665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cron Version: 3.0pl1-127 Severity: important Dear Maintainer, I have a file in /etc/cron.d that runs jobs as a user that is not in /etc/passwd, but is in my NIS passwd database. When I reboot the system the job never runs, and there is no error message in the logs. Other jobs in /etc/cron.d that have entries in /etc/passwd work fine. If I stop and start cron using systemctl the job with the user that is not in /etc/passwd but is in the NIS passwd database runs as scheduled. I believe this is a problem with the start up order for cron. On my system cron is starting up before ypbind. I think it should be starting up afterwards. I am not enough of an expert in systemd to figure out how to set up dependencies for cron to fix this. -- Package-specific info: --- EDITOR: not set --- /usr/bin/editor: /usr/bin/vim.gnome --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 36008 Oct 25 2014 /usr/bin/crontab --- /var/spool/cron: drwxr-xr-x 5 root root 48 Aug 29 2007 /var/spool/cron --- /var/spool/cron/crontabs: drwx-wx--T 2 root crontab 29 Apr 28 13:54 /var/spool/cron/crontabs --- /etc/cron.d: drwxr-xr-x 2 root root 105 Apr 26 14:51 /etc/cron.d --- /etc/cron.daily: drwxr-xr-x 2 root root 4096 Apr 28 11:39 /etc/cron.daily --- /etc/cron.hourly: drwxr-xr-x 2 root root 25 Apr 26 12:47 /etc/cron.hourly --- /etc/cron.monthly: drwxr-xr-x 2 root root 84 Apr 26 14:35 /etc/cron.monthly --- /etc/cron.weekly: drwxr-xr-x 2 root root 90 Apr 26 14:35 /etc/cron.weekly -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages cron depends on: ii adduser 3.113+nmu3 ii debianutils 4.4+b1 ii dpkg 1.17.25 ii init-system-helpers 1.22 ii libc62.19-18 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii lsb-base 4.1+Debian13+nmu1 Versions of packages cron recommends: ii sendmail-bin [mail-transport-agent] 8.14.4-8 Versions of packages cron suggests: ii anacron2.3-23 pn checksecurity ii logrotate 3.8.7-1+b1 Versions of packages cron is related to: pn libnss-ldap pn libnss-ldapd pn libpam-ldap pn libpam-mount ii nis 3.17-33 ii nscd 2.19-18 -- no debconf information --- End Message --- --- Begin Message --- Source: cron Source-Version: 3.0pl1-129 We believe that the bug you reported is fixed in the latest version of cron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated cron package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 11 Mar 2018 22:38:06 +0100 Source: cron Binary: cron Architecture: source i386 Version: 3.0pl1-129 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Description: cron - process scheduling daemon Closes: 767016 783665 801384 819832 864466 Changes: cron (3.0pl1-129) unstable; urgency=medium . * Acknowledge NMU * debian/cron.init, debian/cron.service: Make sure cron is started last and stopped first, with patch provided by Harald Dunke (Closes: #767016, #801384,