search for: received_sighup

Hi folks, I have successfully compiled and run OpenSSH 4.1p1 on NCR MPRAS: $ uname -a UNIX_SV support1 4.0 3.0 3446 Pentium Pro(TM)-EISA/PCI $ However, I have found one pretty critical problem, arising from the way that MPRAS handles changes to the IP stack. Background: To update any of the IP or TCP configuration options, system administrators should use the program "tcpconfig".

> 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

...ss of generating the server key and yet to install the sighup handler. I could fix this by putting the installation of sighup signal handler before the key generation step. It works fine as sighup handler keeps handling the sighup signals and then later on re-reads the configuration file since received_sighup variable is set to 1. My question is by making this change, will I be creating any security hole? Is there a better way to fix it? Is there a reason why signal handlers are not installed first? Any help will be greatly appreciated. Thanks, Dm

...ck_out, int *newsock, int *config_s) * the daemon is killed with a signal. */ for (;;) { + if (ostartups != startups) { + setproctitle("[listener] %d/%d/%d startups", + startups, options.max_startups_begin, options.max_startups); + ostartups = startups; + } if (received_sighup) { if (!lameduck) { debug("Received SIGHUP; waiting for children");