Date: Tue, 24 Mar 1998 18:27:46 -0500 (EST) From: Dave Smith <dvsmith@menger.eecs.stevens-tech.edu> To: David Shanes <dshanes@personalogic.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Sockets stuck in CLOSE_WAIT Message-ID: <Pine.GSO.3.94.980324182513.14696A-100000@menger.eecs.stevens-tech.edu> In-Reply-To: <016801bd575d$2373f960$1d43a8c0@shanes.personalogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for your quick response. I found the problem, and it was due to a poor assumption on my part. I did not realize that the filehandle the socket returned was NOT set close-on-exec. So the sockets were open in programs after the exec, which meant they wouldn't close. After a bit of use of fstat and netstat -A, I found this. David Smith On Tue, 24 Mar 1998, David Shanes wrote: > Are you aborting the Server? You should use the shutdown(int skt, int flag) > command to ensure it gracefully shuts down the server. > > David > > _____________________________________________________ > David Shanes 7535 Metropolitan Drive > dshanes@personalogic.com San Diego, CA 92108 > Database Developer (619) 220-5800 x228 > PersonaLogic, Inc. (619) 220-5899 (fax) > http://www.PersonaLogic.com > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.94.980324182513.14696A-100000>