Displaying 2 results from an estimated 2 matches for "ostartups".
Did you mean:
startups
2020 Jan 21
3
Instrumentation for metrics
> This makes me think that the syslog approach is probably the way to go
Yeah, right.
Another idea is to mirror the current preauth load via setproctitle()...
That makes that data accessible even without a syscall (at least the
writing of the data - quering needs syscalls, right), so that can be
kept up-to-date and allows a high monitoring frequency as well.
Multiple instances of SSHd (on
2020 Jan 21
2
Instrumentation for metrics
...New Zealand
diff --git a/sshd.c b/sshd.c
index 6129b0a..debbdcb 100644
--- a/sshd.c
+++ b/sshd.c
@@ -1005,7 +1005,7 @@ server_accept_loop(int *sock_in, int *sock_out,
int *newsock, int *config_s)
{
fd_set *fdset;
int i, j, ret, maxfd;
- int startups = 0, listening = 0, lameduck = 0;
+ int ostartups = -1, startups = 0, listening = 0, lameduck = 0;
int startup_p[2] = { -1 , -1 };
char c = 0;
struct sockaddr_storage from;
@@ -1029,6 +1029,11 @@ server_accept_loop(int *sock_in, int *sock_out,
int *newsock, int *config_s)
* the daemon is killed with a signal.
*/
for (;;) {
+...