* Roman Drahtmueller wrote on Thu, Jun 27, 2002 at 12:16 +0200:
Actually, rcsshd restart should stop the daemon with the pid from /var/run/sshd.pid. Then a new daemon would start up, writing its pid to the same file. The running instances of sshd which handle active connections should not get touched. There used to be a killall to nuke running daemons, but this is hundreds of years ago.
Well, but *I* did additionally a "killall" on the consolse, and there was no sshd process running before start.
To make sure it works, I usually do the following: [...] Yes, I did it very similar.
Any hints?? What did I wrong? And much more important: How do I make this stuff secure?
rpm -Vv openssh will give you a hint about what has been modified.
Here is a full list: S.5....T c /etc/ssh/sshd_config sshd_config, since I set "UsePrivilegeSeparation yes". But no chroot, no sshd user. How do I make this stuff secure? oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.