Date: Tue, 01 Mar 2011 07:47:38 +0100 From: Andrea Venturoli <ml@netfence.it> To: freebsd-stable@freebsd.org Subject: Re: statd/lockd startup failure Message-ID: <4D6C968A.3040400@netfence.it> In-Reply-To: <4D5D8DF0.8080900@netfence.it> References: <201102091420.p19EKJ5u001268@m5p.com> <AANLkTi=2vA=C8B=NEaGrPgGNv2JJr9KEDJps8uoy8_92@mail.gmail.com> <20110217032858.GA17686@icarus.home.lan> <4D5D8DF0.8080900@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/17/11 22:06, Andrea Venturoli wrote: >> I >>> seem to remember a similar problem I had a long time ago. I opted to >>> use a consistent, not-used port and haven't seen the problem since >>> (this was years ago, so I can't remember if the error you're seeing >>> was identical to mine). >>> >>> /etc/rc.conf: >>> rpc_statd_flags="-p 898" >>> rpc_lockd_flags="-p 4045" > > I have: > rpc_statd_flags="-p 918" > rpc_lockd_flags="-p 868" > > > Still statd occasionally fails to start. > > It might be that something else has already bound to port 918, though I > don't know what. > I'll check as soon as I have the chance. It happened this morning: lockd could not start and I verified it was an NFS mount which used port 868 as a client. Now I'm trying the noresvport to mount_nfs... bye av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D6C968A.3040400>