Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.unix.questions
Subject: Re: How does one specify 'second Tuesday' in a crontab?
Message-ID: <128@crdos1.crd.ge.COM>
Date: 24 Aug 89 13:17:19 GMT
References: <7613@c3pe.UUCP> <1794@crdgw1.crd.ge.com> <9805@alice.UUCP>
Distribution: usa
Organization: GE Corp R&D Center
Lines: 25

In article <9805@alice.UUCP>, debra@alice.UUCP (Paul De Bra) writes:
> In article <1794@crdgw1.crd.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes:
> >The implementation of cron is really stupid! They could have allowed
> >both day of week and day of month with two lines and then anded the day
> >of week/month fields to do what you want.
> >
> 
> The implementation that takes the "or" of day of month and day of week
> is not just stupid, it is wrong.

  Well, if functioning just as the man page indicates it should is
wrong, then it is. However, I always figured that if it worked as
documented it was correct. Here's an exerpt from the man page:


	  Note that the	specification of days may be made by two
	  fields (day of the month and day of the week). If both are
	  specified as a list of elements, both	are adhered to.	 For
	  example, 0 0 1,15 * 1	would run a command on the first and
	  fifteenth of each month, as well as on every Monday.	To
	  specify days by only one field, the other field should be
	  set to * (for	example, 0 0 * * 1 would run a command only on
	  Mondays).
  It doesn't work the way I thought it did, or even the way I think is
*should*, but it works as documented.