Subject: misc/2806: [dM] crontab(5) confusing and incomplete
To: None <firstname.lastname@example.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Date: 10/05/1996 18:55:50
>Synopsis: [dM] crontab(5) confusing and incomplete
>Responsible: misc-bug-people (Misc Bug People)
>Arrival-Date: Sat Oct 5 16:05:01 1996
>Originator: der Mouse
>Release: 1.2_BETA (supped July 3rd), $Id: crontab.5,v 184.108.40.206 1994/01/26 19:09:33 jtc Exp $
Any (noticed on Sun-3/260)
System: NetBSD Twig.Rodents.Montreal.QC.CA 1.2_BETA NetBSD 1.2_BETA (TWIG) #0: Tue Sep 3 00:45:26 EDT 1996 mouse@Twig.Rodents.Montreal.QC.CA:/mouse/sources/working-usr-src/sys/arch/sun3/compile/TWIG sun3
crontab(5) documents the month numbers as "0-12", which is
confusing unless 0 and 12 mean the same thing - but unlike the
day-of-week numbers, no such mention is made. It also does not
document the @reboot, @hourly, etc, possibilities.
UTSLing reveals that month numbers are actually 1 through 12,
which is to be expected for compatability reasons.
% man 5 crontab
Change the 0-12 range to 1-12. Preferably, also write
documentation for the @ commands.
I may get around to doing this myself; if so, I'll send in an
addendum to this PR.
01 EE 31 F6 BB 0C 34 36 00 F3 7C 5A C1 A0 67 1D