Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!midway!mimsy!jds
From: jds@cs.umd.edu (James da Silva)
Newsgroups: comp.os.minix
Subject: Re: FvK's Cron bug
Keywords: Cron Advanced Minix
Message-ID: <35618@mimsy.umd.edu>
Date: 14 Jun 91 03:43:16 GMT
References: <9106031294@tisle.uucp> <1991Jun13.123330.22543@nmrdc1.nmrdc.nnmc.navy.mil>
Sender: news@mimsy.umd.edu
Organization: University of Maryland, Department of Computer Science
Lines: 35

In article <1991Jun13.123330.22543@nmrdc1.nmrdc.nnmc.navy.mil>
rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) writes:
>In article <9106031294@tisle.uucp> edwards@tisle.uucp (Colten Edwards) writes:
>>The recently posted cron by FwK does not work with the following.
>>10 	*	*	*	1-7 
>>This entry will work everyday except Sunday... I am sure the fix will
>>not take much, and I'll start looking tonight at what can be done to rectify
>>the situation.
>>
>Try 10 * * * 0-6
>
>In every cron I've used the days are numbered 0,1 2,3,4,5,6 starting with
>Sunday.

Hi Mike!

Looks like another one of those BSD vs SYSV things.  Doing an informal
survey of man pages around here I find:

7th Edition	1..7 w/Sunday=7
4.3 Tahoe  	same
4.3 Reno	same
Ultrix		same
Encore UMAX	same
SunOS 3.2	same
10th Edition    0..6 w/Sunday=0
SunOS 4.1.1	0..7 w/Sunday=0 or Sunday=7

Perhaps supporting both 0 and 7 for Sunday is the least puzzling thing for
a cron implementation to do these days.

Jaime
...........................................................................
: domain: jds@cs.umd.edu				     James da Silva
: path:   uunet!mimsy!jds		    Systems Design & Analysis Group