>Number:         2806
>Category:       misc
>Synopsis:       [dM] crontab(5) confusing and incomplete
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct  5 16:05:01 1996
>Last-Modified:
>Originator:     der Mouse
>Organization:
	Dis-
>Release:        1.2_BETA (supped July 3rd), $Id: crontab.5,v 1.1.1.5 1994/01/26 19:09:33 jtc Exp $
>Environment:
	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


>Description:
	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.
>How-To-Repeat:
	% man 5 crontab
>Fix:
	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.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     01 EE 31 F6 BB 0C 34 36  00 F3 7C 5A C1 A0 67 1D
>Audit-Trail:
>Unformatted: