Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!news-peer.gsl.net!news.gsl.net!howland.erols.net!www.nntp.primenet.com!nntp.primenet.com!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail
From: brian@awfulhak.demon.co.uk (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Hung sockets and innd problem
Date: 12 Dec 1996 16:37:41 -0000
Organization: Coverform Ltd.
Lines: 21
Message-ID: <58pccl$dk6@anorak.coverform.lan>
References: <craigs-ya023180001112960847000001@news.os.com>
NNTP-Posting-Host: anorak.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32468
Craig Shrimpton (craigs@os.com) wrote:
: Folks,
: I'm running 2.1-STABLE and have been experiencing a problem with news feeds
: stuck in a CLOSE_WAIT state. It seems only a reboot will fix it. What is
: causing this and can I clear it without rebooting?
What sort of machine is on the other side ? This CLOSE_WAIT is because the
other side hasn't agreed to go away. It shouldn't happen when both sides
are well behaved. It does time out eventually, but it takes quite some
time !
I recall seing a setsockopt() call in the ftp.c code that *may* reuse a
socket endpoint that's not completely gone away, but I'm not sure by any
stretch of the imagination. Have a peruse of the setsockopt man page....
--
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....