I hope someone can help. I've installed 2.9p2 on a number of AIX boxes and it works great. The problem is that a HUGE >700 number of defunct processes get generated by sshd. Did I do something wrong ? Any suggestions ? Please email chuck at fiu.edu as I don't subscribe to the list. TIA, Chuck -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2834 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20010914/ecb0f5d6/attachment.bin
How are you starting the initial sshd daemon? If through /etc/inittab, make sure that the action is not set to "respawn", but is "once". Better would be to just call a script that starts the daemon after checking some things. Perhaps I'm off-base here; in any case, I'd be happy to help you if you provide more information. --Sandy>I hope someone can help. I've installed 2.9p2 on a number of AIX boxes and >it works great. >The problem is that a HUGE >700 number of defunct processes get generated >by sshd. Did I do >something wrong ? Any suggestions ? > >Please email chuck at fiu.edu as I don't subscribe to the list. > > >TIA, >Chuck > > >Content-Type: application/x-pkcs7-signature; > name="smime.p7s" >Content-Disposition: attachment; > filename="smime.p7s" > >Attachment converted: home:smime.p7s (????/----) (0006FBEC)-- ------------------------------------------------ sandor w. sklar | Non impediti unix systems administrator | ratione stanford university itss-css | cogitationis -------------------------------------------------
Chuck,
There is a better way to manage sshd under AIX. The AIX SRC (system
resource controller) can control the SSH daemon, and even respawn it
should it fall over -- without generating tonnes of unneccessary children.
As root, execute:
mkssys -s sshd -u 0 -p /usr/sbin/sshd -a '-D' -G ssh -R -S -n 15 -f
9
Change /usr/sbin/sshd to wherever you have sshd installed. The -R
automatically restarts SSH if it ever falls over. SSH requires the -D
option to prevent it forking (a requirement of the SRC).
You can now start sshd using the command:
startsrc -s sshd
and stop it using (if you just kill it, SRC will start a new one!):
stopsrc -s sshd
You can set it to auto start on boot by adding this line to the end of
/etc/rc.tcpip
start /usr/sbin/sshd "$src_running"
Hope this is useful!
--------------------------------------------------------
Doug Manton, AT&T EMEA Commercial Security Solutions
E: demanton at att.com
--------------------------------------------------------
"If privacy is outlawed, only outlaws will have privacy"