Date: Sat, 31 May 1997 02:55:46 +0900 From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp> To: jdp@polstra.com Cc: max@wide.ad.jp, current@freebsd.org, wollman@freebsd.org Subject: loopback i/f bug (?) [ was Re: Some trouble with SCSI HD] Message-ID: <199705301755.CAA00639@bourbon.sfc.wide.ad.jp> In-Reply-To: Your message of "Fri, 30 May 1997 09:44:43 -0700" References: <199705301644.JAA28650@austin.polstra.com>
index | next in thread | previous in thread | raw e-mail
>> 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.
jdp> I noticed this too when I tried to CVSup to localhost. I
jdp> don't think it has anything to do with SCSI. I think it's a
jdp> networking bug in the loopback interface, exposed by CVSup's
jdp> unusual traffic patterns.
jdp> If you CVSup to yourhost.domain.name instead of localhost, it
jdp> works fine.
Looks like you are right, John. I removed /usr/ports, and re-cvsup'ed
the ports-all collection from my machine, specifying the FQDN this
time, instead of ``localhost'' and it went OK.
So, as you say, it's more than likely that loopback interface has some
problem.
Thanks for your suggestion. It really helped!
Cheers,
Max
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705301755.CAA00639>