From owner-svn-src-head@freebsd.org Fri Jun 8 19:11:05 2018 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F41EAFD3050; Fri, 8 Jun 2018 19:11:04 +0000 (UTC) (envelope-from pstef@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD7E86FBCD; Fri, 8 Jun 2018 19:11:04 +0000 (UTC) (envelope-from pstef@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1403) id A5CB21BC7D; Fri, 8 Jun 2018 19:11:04 +0000 (UTC) Date: Fri, 8 Jun 2018 21:11:04 +0200 From: "Piotr P. Stefaniak" To: Gleb Smirnoff Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r334817 - in head/usr.sbin/cron: cron crontab lib Message-ID: <20180608191104.GA88867@freefall.freebsd.org> References: <201806072238.w57Mcehx011811@repo.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <201806072238.w57Mcehx011811@repo.freebsd.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2018 19:11:05 -0000 On 2018-06-07 22:38:40, Gleb Smirnoff wrote: >Author: glebius >Date: Thu Jun 7 22:38:40 2018 >New Revision: 334817 >URL: https://svnweb.freebsd.org/changeset/base/334817 > >Log: > Add new functionality and syntax to cron(1) to allow to run jobs at a > given interval, which is counted in seconds since exit of the previous > invocation of the job. Example user crontab entry: > > @25 sleep 10 > > The example will launch 'sleep 10' every 35 seconds. This is a rather > useless example above, but clearly explains the functionality. > > The practical goal here is to avoid overlap of previous job invocation > to a new one, or to avoid too short interval(s) for jobs that last long > and doesn't have any point of immediate launch soon after previous run. > > Another useful effect of interval jobs can be noticed when a cluster of > machines periodically communicates with a single node. Running the task > time based creates too much load on the node. Running interval based > spreads invocations across machines in cluster. Note that -j/-J won't > help in this case. > > Sponsored by: Netflix Missing a Relnotes tag, possibly.