Date: Thu, 20 Apr 2017 03:39:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 104809] cron(8): incorrect cron behavior with mday field = "*/N" Message-ID: <bug-104809-8-DVhGtshiZc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-104809-8@https.bugs.freebsd.org/bugzilla/> References: <bug-104809-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D104809 Kyle Evans <bsdports@kyle-evans.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bsdports@kyle-evans.net --- Comment #1 from Kyle Evans <bsdports@kyle-evans.net> --- Hello! It's been a long time with no response and you probably know this by now, b= ut for anyone that may stumble upon this- this is actually intended, albeit qu= irky to the uninitiated, behavior. The expression "*/5" is not mathematical division but instead a step functi= on, where "/5" indicates every 5 units of the range "*". crontab(5) documents "= *" as expanded to "first-last", and allowed values for day of the month being 1-31. This would indicate that "*/5" expands to "start-end/5" to "1-31/5," meaning "every 5 units starting at 1." That being said, 1-31/5 *should* fire at 1,6,11,16,21,26,31. If it were mathematical division, it would instead fire at 5,10,15,20,25,30. "Works as intended" --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-104809-8-DVhGtshiZc>