Date: Tue, 25 Jan 2022 22:17:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 210538] [feature request] limit number of running instances in crontab Message-ID: <bug-210538-227-LkHHpx88S4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210538-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210538 Mikhail Teterin <mi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glebius@FreeBSD.org --- Comment #2 from Mikhail Teterin <mi@FreeBSD.org> --- (In reply to Alan Somers from comment #1) > This feature was added in SVN r334817. That's related, but not quite the same thing... The commit by @glebius provides for running "every X seconds" -- and is useful for frequent jobs. But it'd be difficult to use even with periodic(8) -- which still does its own locking -- because you cannot specify the desired schedule time. The feature I envisioned was a safeguard against jobs running unusually long. The feature implemented in r334817 is for jobs, that do usually run long... Try rephrasing the periodic-entries in today's /etc/crontab to use Gleb's new syntax -- so that /usr/sbin/periodic no longer needs its own locking. You cannot... Please, reopen this PR. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210538-227-LkHHpx88S4>