vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On 3/19/07, Han Boetes <han@mijncomputer.nl> wrote: > I just had two cronjobs which were set on the same time and the > first match was executed and the second was ignored. Maybe I misunderstand your description of the problem, but it seems to work fine for me using recent -current code: $ crontab -l # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.lDdOgE4987 installed on Mon Mar 19 20:56:58 2007) # (Cron version V5.0 -- $OpenBSD: crontab.c,v 1.51 2007/02/19 00:08:38 jmc Exp $) SHELL=/bin/sh #minute hour mday month wday command 58 * * * * echo "job 1" >>~/foo 58 * * * * echo "job 2" >>~/foo $ cat ~/foo job 1 job 2 $ dmesg|head -n2 OpenBSD 4.1-current (GENERIC) #0: Thu Mar 15 03:20:13 PDT 2007 root@tigger.local:/usr/src/sys/arch/i386/compile/GENERIC > Another thing, crontab -l shows this header. > > # DO NOT EDIT THIS FILE - edit the master and reinstall. > # (/tmp/crontab.hwekl21478 installed on Tue Mar 20 03:34:00 2007) > # (Cron version V5.0 -- $OpenBSD: crontab.c,v 1.51 2007/02/19 00:08:38 jmc Exp $) > > Wouldn't it be nicer to skip this header? Yes, perhaps this header would in fact confuse noobs, but isn't that part of official obsd policy? Regards... Greg |