home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!sgi!odin!sam.wpd.sgi.com!pj
- From: pj@sam.wpd.sgi.com (Paul Jackson)
- Subject: Re: correction re: cron problem
- Message-ID: <1992Jul25.014756.21836@odin.corp.sgi.com>
- Sender: news@odin.corp.sgi.com (Net News)
- Nntp-Posting-Host: sam.wpd.sgi.com
- Reply-To: pj@sgi.com
- Organization: Silicon Graphics, Research & Development
- References: <31518@adm.brl.mil>
- Date: Sat, 25 Jul 1992 01:47:56 GMT
- Lines: 30
-
- In article <31518@adm.brl.mil>, johnson@euler.jsc.nasa.gov (Stan Johnson) writes:
- |>
- |> #min hour daymo month daywk cmd
- |> 32 4 22-28 * 0 /etc/my_program
- |>
- |> Cron actually ran my sample program only yesterday (22nd) and today, as
- |> if I had entered "*" for daywk.
-
- Using both daymo and daywk to specify the day(s) to run a command
- does not result in only running the command on the days meeting
- both conditions, but on days meeting either condition. These two
- fields are combined as if with an OR, not an AND, operator.
-
- To quote 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).
-
-
- --
-
- I won't rest till it's the best ...
- Software Production Engineer
- Paul Jackson (pj@sgi.com), x1373
-