Your message dated Tue, 8 Oct 2024 15:39:41 +0200
with message-id <[email protected]>
and subject line Re: [email protected]
has caused the Debian Bug report #1081830,
regarding cron: Cron cannot process '1st sunday of the month' directive
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.)
--
1081830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081830
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cron
Version: 3.0pl1-189
Severity: important
Hello.
I was trying to execute a command on the 1st sunday of the month at
9:30. The directive for such a command should be:
30 9 1-7 * 7 command
\ / \ / | |
\/ | | +---- (or 0) Sunday
| | +------ any month
| +--------- 1st week (days of month 1 to 7)
+------------- 9:30
However, on Sept. Sun. 15, the command was executed. And 15 is not
within "1-7"...
-- Package-specific info:
--- EDITOR:
not set
--- /usr/bin/editor:
/usr/bin/nano
--- /usr/bin/crontab:
-rwxr-sr-x 1 root crontab 51024 Mar 26 19:08 /usr/bin/crontab
--- /var/spool/cron:
drwxr-xr-x 5 root root 4096 May 21 2011 /var/spool/cron
--- /var/spool/cron/crontabs:
drwx-wx--T 2 root crontab 4096 Sep 15 10:57 /var/spool/cron/crontabs
--- /etc/cron.d:
drwxr-xr-x 2 root root 4096 May 23 07:52 /etc/cron.d
--- /etc/cron.daily:
drwxr-xr-x 2 root root 4096 Sep 14 07:16 /etc/cron.daily
--- /etc/cron.hourly:
drwxr-xr-x 2 root root 4096 Mar 30 07:28 /etc/cron.hourly
--- /etc/cron.monthly:
drwxr-xr-x 2 root root 4096 Apr 30 18:30 /etc/cron.monthly
--- /etc/cron.weekly:
drwxr-xr-x 2 root root 4096 Aug 31 08:19 /etc/cron.weekly
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 6.10.9-686-pae (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cron depends on:
ii cron-daemon-common 3.0pl1-189
ii init-system-helpers 1.66
ii libc6 2.40-2
ii libpam-runtime 1.5.3-7
ii libpam0g 1.5.3-7
ii libselinux1 3.7-3
ii sensible-utils 0.0.24
Versions of packages cron recommends:
ii nullmailer [mail-transport-agent] 1:2.2+10~g7ed88a0-6
Versions of packages cron suggests:
pn anacron <none>
ii bat 0.24.0-1+b3
pn checksecurity <none>
ii logrotate 3.22.0-1
ii supercat 0.5.7-1
Versions of packages cron is related to:
pn libnss-ldap <none>
pn libnss-ldapd <none>
pn libpam-ldap <none>
pn libpam-mount <none>
pn nis <none>
pn nscd <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Thomas Nemeth a écrit :
> Le dimanche 15 septembre 2024, 20:24:21 CEST Khaznadar Georges a écrit :
> > Hello Thomas, thank you for the bug report.
> >
> > I believe that your report is not about a bug, but about an unclear
> > explanation in cron and crontab's manpages.
>
> Well, to be more precise, it's a missing translation in the
> french version of the manpage that lead me to think it was
> an "AND" for all the fields. Friends with the english version
> pointed me to a part of the manpage that explained the
> observed behavior.
>
> I had, since then, fixed my crontab entry :)
>
> I think we can close the BR.
> Thanks a lot.
>
> Regards,
>
> Thomas.
>
>
>
--
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 ---
