Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Jan 2000 01:23:54 +0900
From:      Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To:        "Jeffrey J. Libman" <jeffrl@wantabe.com>
Cc:        stable@freebsd.org, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject:   Re: rpc.statd won't fire on friday's build 
Message-ID:  <200001191623.BAA01247@zodiac.mech.utsunomiya-u.ac.jp>
In-Reply-To: Your message of "Sun, 16 Jan 2000 07:49:58 CST." <Pine.BSF.4.21.0001160747050.8327-100000@cutter.wantabe.com> 
References:  <Pine.BSF.4.21.0001160747050.8327-100000@cutter.wantabe.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

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?200001191623.BAA01247>