bug#56866: [Shepherd] inetd connections not correctly counted?

2023-04-27 Thread Ludovic Courtès
Hi, Ludovic Courtès skribis: > We recently experienced a bug on berlin.guix where we’d be locked out of > SSH access because shepherd (0.9.1) would say that the maximum > connection number on the sshd inetd service had been reached. This (1) the problem has not occurred again in the intervening

bug#56866: [Shepherd] inetd connections not correctly counted?

2022-08-13 Thread Joshua Branson via Bug reports for GNU Guix
Ludovic Courtès writes: > Hi, > > Ludovic Courtès skribis: > >> We recently experienced a bug on berlin.guix where we’d be locked out of >> SSH access because shepherd (0.9.1) would say that the maximum >> connection number on the sshd inetd service had been reached. Perhaps we could merge bug

bug#56866: [Shepherd] inetd connections not correctly counted?

2022-08-09 Thread Ludovic Courtès
Hi, Ludovic Courtès skribis: > We recently experienced a bug on berlin.guix where we’d be locked out of > SSH access because shepherd (0.9.1) would say that the maximum > connection number on the sshd inetd service had been reached. On berlin.guix, which is getting hammered, we see things like

bug#56866: [Shepherd] inetd connections not correctly counted?

2022-08-01 Thread Ludovic Courtès
Hi, We recently experienced a bug on berlin.guix where we’d be locked out of SSH access because shepherd (0.9.1) would say that the maximum connection number on the sshd inetd service had been reached. That threshold is a feature (see ‘max-connections’ in ) but there’s a possibility in this case