From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Fri Mar 30 23:56:01 EDT 2018 Message-ID: <66C4B182F078035299E210A587AE1A98@felloff.net> Date: Sat, 31 Mar 2018 05:55:55 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] rimport error: tlsclient: auth_proxy: fauth_proxy start: too much activity In-Reply-To: 4E866EE6-3A97-49AC-ACE4-1AC352A635DB@stanleylieber.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: structured rich-client deep-learning-scale polling-based solution 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