-----BEGIN PGP SIGNED MESSAGE-----
Marius Andreiana wrote:
| On Wed, 2005-02-02 at 20:17 -0600, Eric Vought, Technical Director
|>OK, the problem is that service sshd reload and service sshd restart are
|>not working. They are SIGHUPping the wrong process IDs. I figured this
|>out when I realized that not all of my ssh sessions were closing when I
|>reloaded the configuration. The session which was closing was the one
|>which was mistakenly shut down by service sshd reload/restart.
|>When I HUP the process myself, everything suddenly works.
| If true, this would be a bug. Stop has
| echo -n $"Stopping $prog:"
| killproc $SSHD -TERM
| and restart has stop() start().
| Could you please test more? init.d script looks ok to me.
OK, sorry this has taken some time to follow up. I needed time to fiddle
with the system some more in order to write a good bug report.
The problem is no longer reproducible after a reboot. It looks like
/var/run/sshd.pid may have gotten corrupted in some manner, which was
fixed when the system came back up (unrelated upgrade).
I am extremely reluctant to muck further with a production server, but
have a local FC3 box to break now. The odd thing is that I can only
reproduce the behavior when the content of the .pid file is *wrong* not
merely non-existant or empty. If the file is missing or empty, killproc
falls back to using pidof to return all sshd processes, not just the
first found, which would have (and does) work correctly. Further, I know
from an IDS log that the file did exist and was non-empty. I cannot, at
the moment, think of how the pidfile corruption could plausibly occur,
and, in any case, it is probably not FC3's fault.
To sum: I do not think there is enough to open a bug. Chalk one up to
Diversity Ink, Morgan Family Enterprises
Web Hosting and Site Design for Small Business and Not-for-Profit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----