Date: Tue, 25 Mar 2014 10:09:49 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Server sockets staying in CLOSED for extended periods Message-ID: <CAN6yY1veOKGtMNHR567%2B-nUDQo7dYQTP5x3Nf3CSj9PK86dktQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
There has been a long thread on stable about sshd processes being hung due to sockets remaining in a CLOSED state for extended periods in 10-stable. This did not seem to be happening with 9.2. (Not sure about 10.0.) Was here a change in the network stack on 10 that would have kept CLOSED sockets around for extended intervals? Should sshd processes hang for extended periods (forever?) unless killed (KILL)? I also wonder if a daemon process should refuse to exit if a closed socket remains. Any suggestions would help. the full thread with a great deal of detail is in stable with the subject "sshd with zombie process on FreeBSD 10.0-STABLE - workaround". -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1veOKGtMNHR567%2B-nUDQo7dYQTP5x3Nf3CSj9PK86dktQ>