Date: Thu, 20 Jan 2000 14:32:36 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: "Jeffrey J. Libman" <jeffrl@wantabe.com>, stable@freebsd.org, current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: rpc.statd won't fire on friday's build Message-ID: <200001200532.OAA16660@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | raw e-mail | index | archive | help
Oops, my loopback (lo0) was down. It's a pilot error. Sorry for the false alarm. `portmap' is OK in -CURRENT. Jeffrey, your problem may be the same as mine. You had better check `network_interfaces' in /etc/rc.conf. It should have `lo0' together with all other network interfaces. Or, it should have just one word, "auto". Kazu >I am experiencing the same problem on the 4.0-CURRENT system >built from the source around Saturday. Another -CURRENT box, >for which 'make world' was done from the source about a week ago, >appears to have no problem. > >I suspect `portmap' is somewhat broken. In addition to `rpc.statd', >`nfsd' and `mountd' are also unable to register ports. > >nfsd:[88]: can't register with udp portmap >mountd[86]: can't register mount > >Kazu > >>no idea what i've done here. >> >>friday's cvsup and build...new kernel...installed on 2 systems. on one of >>the systems, rpc.statd will not run, gets: >> >>rpc.statd: unable to register (SM_PROG, SM_VERS, udp) >> >>this particular system has about 50 ip's assigned to lo0...and that has >>worked fine as is for months, inspite of all the verbage here about >>netmasks and such. loopback IS configured. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001200532.OAA16660>