Your message dated Mon, 28 Aug 2023 18:33:53 +0200 with message-id <[email protected]> and subject line Re: run-parts omits some scripts in /etc/cron.daily has caused the Debian Bug report #1014089, regarding run-parts omits some scripts in /etc/cron.daily 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.) -- 1014089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014089 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: debianutils Version: 4.11.2 If I modify /etc/crontab to use run-parts --verbose, then I get these messages per EMail: run-parts: executing /etc/cron.daily/01_hello Thu Jun 30 06:25:01 CEST 2022 hi mom run-parts: /etc/cron.daily/01_hello exited with return code 1 run-parts: executing /etc/cron.daily/02_hello Thu Jun 30 06:25:01 CEST 2022 hi mom run-parts: executing /etc/cron.daily/apache2 run-parts: executing /etc/cron.daily/apt-compat run-parts: executing /etc/cron.daily/aptitude run-parts: executing /etc/cron.daily/brave-browser run-parts: executing /etc/cron.daily/cracklib-runtime run-parts: executing /etc/cron.daily/debsums run-parts: executing /etc/cron.daily/dpkg run-parts: executing /etc/cron.daily/drop_upgrade_stamp run-parts: executing /etc/cron.daily/etckeeper run-parts: executing /etc/cron.daily/google-chrome run-parts: executing /etc/cron.daily/logrotate run-parts: executing /etc/cron.daily/man-db run-parts: executing /etc/cron.daily/mdadm run-parts: executing /etc/cron.daily/ntp run-parts: executing /etc/cron.daily/spamassassin run-parts: executing /etc/cron.daily/sysstat run-parts: executing /etc/cron.daily/vivaldi Please compare that to the contents of /etc/cron.daily: # ls -al /etc/cron.daily total 96 drwxr-xr-x 2 root root 4096 Jun 30 07:51 . drwxr-xr-x 228 root root 20480 Jun 29 14:33 .. -rw-r--r-- 1 root root 102 Jun 11 2015 .placeholder -rwxr-xr-x 1 root root 38 Jun 29 12:01 01_hello -rwxr-xr-x 1 root root 32 Jun 29 11:54 02_hello -rwxr-xr-x 1 root root 539 Jan 25 2017 apache2 -rwxr-xr-x 1 root root 1478 Mar 8 2019 apt-compat -rwxr-xr-x 1 root root 314 Nov 8 2014 aptitude lrwxrwxrwx 1 root root 39 Jun 24 08:00 brave-browser -> /opt/brave.com/brave/cron/brave-browser -rwxr-xr-x 1 root root 355 Oct 17 2014 bsdmainutils.dpkg-remove lrwxrwxrwx 1 root root 27 Jun 27 11:03 clamscan.daily.sh -> ../clamav/clamscan.daily.sh -rwxr-xr-x 1 root root 384 Oct 5 2014 cracklib-runtime -rwxr-xr-x 1 root root 595 Feb 25 2020 debsums -rwxr-xr-x 1 root root 1298 Jan 9 2021 dpkg -rwxr-xr-x 1 root root 181 Jul 7 2016 drop_upgrade_stamp -rwxr-xr-x 1 root root 205 Jul 18 2016 etckeeper lrwxrwxrwx 1 root root 37 Jun 15 03:32 google-chrome -> /opt/google/chrome/cron/google-chrome -rwxr-xr-x 1 root root 377 Aug 24 2018 logrotate -rwxr-xr-x 1 root root 1123 Feb 10 2019 man-db -rwxr-xr-x 1 root root 622 Nov 15 2020 mdadm -rwxr-xr-x 1 root root 1403 Mar 21 2019 ntp -rwxr-xr-x 1 root root 2685 Jan 31 2020 spamassassin -rwxr-xr-x 1 root root 518 Feb 2 2021 sysstat lrwxrwxrwx 1 root root 25 May 11 2021 vivaldi -> /opt/vivaldi/cron/vivaldi What happened to clamscan.daily.sh? Why wasn't it run, but silently ignored? The man page doesn't tell. At least in verbose mode run-parts should list all scripts and explain why some are ignored. And please fix the man page. Thank you very much Harri
--- End Message ---
--- Begin Message ---Control: tags -1 wontfix The manpage is explicit about the behaviour and I will not change it. This is actually a duplicate of #668883.
--- End Message ---
