From owner-freebsd-current Wed Jan 8 09:05:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA17560 for current-outgoing; Wed, 8 Jan 1997 09:05:50 -0800 (PST) Received: from chaos.ecpnet.com (raistlin@chaos.ecpnet.com [204.246.64.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA17555 for ; Wed, 8 Jan 1997 09:05:46 -0800 (PST) Received: from localhost (raistlin@localhost) by chaos.ecpnet.com (8.8.4/8.8.4) with SMTP id LAA21976; Wed, 8 Jan 1997 11:08:52 -0600 (CST) Date: Wed, 8 Jan 1997 11:08:51 -0600 (CST) From: Justen Stepka To: grog@lemis.de cc: FreeBSD current users Subject: Re: What's happened to nfsd and mountd? In-Reply-To: <199701081040.LAA01341@freebie.lemis.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I noticed the same thing, I just thought that I broke something so I *was* planning reinstall. What normally happens is that the system will just hang and I can't abort the process being forced to reboot. On Wed, 8 Jan 1997 grog@lemis.de wrote: :For the past 10 days or so, I haven't been able to build functional :nfsd and mountd: they die with messages like these: : :Jan 8 11:34:38 freebie mountd[1215]: Can't register mount :Jan 8 11:35:16 freebie nfsd:[1261]: can't register with udp portmap : :ktraces show that in each case a sendto fails: : : 577 mountd CALL sendto(0x5,0x465f0,0x38,0,0x46408,0x10) : 577 mountd RET sendto -1 errno 47 Address family not supported by protocol family : 577 mountd CALL write(0x2,0xefbfcb98,0x67) : 577 mountd GIO fd 2 wrote 103 bytes : "Cannot register service: RPC: Unable to send; errno = Address family not supported by protocol family : : " :(don't ask me where stderr goes--I didn't see this message anywhere :when I ran mountd). : :This is apparently not a kernel problem: I can start the versions I :compiled a month ago and which I still have on my laptop, and they run :fine. It's rather puzzling, though, because the source files haven't :changed in that time. I can only assume a library problem somewhere, :but I don't have the time to follow it up. : :Greg :