9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rimport error: tlsclient: auth_proxy: fauth_proxy start: too much activity
Date: Sat, 31 Mar 2018 05:55:55 +0200	[thread overview]
Message-ID: <66C4B182F078035299E210A587AE1A98@felloff.net> (raw)
In-Reply-To: 4E866EE6-3A97-49AC-ACE4-1AC352A635DB@stanleylieber.com

you can try increasing the limit. the reason it spawns processes is that when
one authserver is broken/dead, it wont hang the whole factotum. on the other
hand, we dont want it to forkbomb as well so it can recover once the authserver
is restored.

another approach is to revert to old behaviour once the limit is reached. so
it wont lock up unless you try hard. and maybe then you deserve it?

you could also try to avoid the issue by staggering your cronjobs, so they
wont all hammer in at the same time.

--
cinap


             reply	other threads:[~2018-03-31  3:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31  3:55 cinap_lenrek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-31  3:15 cinap_lenrek
2018-03-31  3:31 ` Stanley Lieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66C4B182F078035299E210A587AE1A98@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).