On Thu, May 04, 2023 at 05:40:10PM -0600, Todd C. Miller wrote:
> I'm fairly certain that doesn't do what you think it does. When I
> tested it "~/10" behaved the same as "~". The step value is not
> even parsed.
Oh I see, it is actually picking a random minute and ignores steps,
so entries run once an hour:
~/10 * * * * -qs touch /tmp/cron-foo.$(date +\%s)
~/10 * * * * -qs touch /tmp/cron-bar.$(date +\%s)
~/10 * * * * -qs touch /tmp/cron-lol.$(date +\%s)
from earlier gave me:
-rw-r--r-- 1 kn wheel 0 May 5 18:08 /tmp/cron-bar.1683295681
-rw-r--r-- 1 kn wheel 0 May 5 19:08 /tmp/cron-bar.1683299281
-rw-r--r-- 1 kn wheel 0 May 5 18:34 /tmp/cron-foo.1683297241
-rw-r--r-- 1 kn wheel 0 May 5 18:11 /tmp/cron-lol.1683295861
-rw-r--r-- 1 kn wheel 0 May 5 19:11 /tmp/cron-lol.1683299461
>
> It sounds like what you want is the proposed syntax "*/~10"
> to use a random offset.
Indeed, thanks.
