Date: Fri, 30 May 1997 09:44:43 -0700 From: John Polstra <jdp@polstra.com> To: max@wide.ad.jp Cc: current@freebsd.org, wollman@freebsd.org Subject: Re: Some trouble with SCSI HD Message-ID: <199705301644.JAA28650@austin.polstra.com> In-Reply-To: <199705300652.PAA00798@bourbon.sfc.wide.ad.jp> References: <199705300652.PAA00798@bourbon.sfc.wide.ad.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199705300652.PAA00798@bourbon.sfc.wide.ad.jp>, Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp> wrote: > I'm running -current from about a week ago. When I run cvsup to get > some files from cvsupd running on localhost, the system freezes. Many > times, the system just goes quiet and no input from console is > accepted. A few other other times, it goes half dead, I mean, I can > traceroute or ping to the system from another machine but nothing > else can be done. > > When I run cvsup and get files from remote system, this doesn't > happen. I noticed this too when I tried to CVSup to localhost. I don't think it has anything to do with SCSI. I think it's a networking bug in the loopback interface, exposed by CVSup's unusual traffic patterns. If you CVSup to yourhost.domain.name instead of localhost, it works fine. I've been meaning to look into this problem, but I haven't gotten around to it. Maybe Garrett will have some ideas. I've added him to the cc list. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705301644.JAA28650>