Bug 217055 - Consolidate random sleeps in periodic scripts

[Cy Schubert]

In message <CAOtMX2jj_GCKjWW8CpapHutwH7OY00WnSWQS5VOuruv6i9Avqw at mail.gmail.c
om>
, Alan Somers writes:
> On Mon, Feb 13, 2017 at 12:01 AM, Cy Schubert <Cy.Schubert at komquats.com> wrot
> e:
> > In message <CAOtMX2gJRuKKwwcHW5ZxTTZAm5Tmb7cVQ1SZEjwnuingYnO-Zg at mail.gmail.
> c
> > om>
> > , Alan Somers writes:
> >> I propose that we remove the various anti-congestion sleeps from
> >> different periodic scripts, and add a single anti-congestion sleep to
> >> the very beginning.  Does this sound like a good idea to all of you?
> >>
> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217055
> >
> > I think the problem with the sleeps is simply the sleeps. My original plan
> > to put my sleep/fetch in the background was shot down by some who thought
> > it wasn't simple enough.
> >
> > Secondly, we don't need sleeps every boot. Ntpd for example only needs a
> > sleep twice a year max to fetch a new leapfile so, to have a sleep every
> > boot would be annoying.
> >
> > The best solution to replace sleeps would be to put a list of files:URLs
> > into a queue to be fetched by fetcher script which would fetch only needed
> > files that boot (or in the case of ntp via periodic.conf twice a year).
> >
> > A single script with a queue of files to fetch with one anti-congestion
> > sleep, preferably in the background.
> >
> > NTP, btw can (will) use the leapfile in /etc/ntp until a fresher copy is
> > fetched.
> >
> > Let's remove all fetching functions from the various rc scripts and queue
> > them up early in a fetcher rc script, preferably in the background if at
> > all possible.
> >
> >
> > --
> > Cheers,
> > Cy Schubert <Cy.Schubert at cschubert.com>
> > FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  http://www.FreeBSD.org
> >
> >         The need of the many outweighs the greed of the few.
> 
> Unfortunately that won't work, Cy.  Some scripts may need to
> dynamically determine what files to fetch, in a way that we can't do
> in a single separate fetcher script.  Worse, some scripts, like
> 300.statistics from sysutils/bsdstats, need to _post_ a URL, not get
> one.

Diverse requirements cannot be addressed by one knob. To assume that 
various applications all have the same sleep requirement won't work.

I suppose we could have an optional single sleep script but we can't 
summarily remove all sleeps and assume all rc and periodic scripts sleep 
for some, one or possibly no applications requiring a sleep at any given 
time. We can have a general sleep but removing the option of others would 
be counter productive. It doesn't make sense to have an arbitrary sleep 
just in case a subsequent script might need it. If we have to, let's either 
reduce the length of the sleeps or put better yet background them.

What's motivating this? Server? Laptop?


-- 
Cheers,
Cy Schubert <Cy.Schubert at cschubert.com>
FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.