portupgrade fails: no locking avaiable

[llx]

yes i do.

sh-2.05b$ rpcinfo -p <CLIENT>
   program vers proto   port  service
    100000    4   tcp    111  rpcbind
    100000    3   tcp    111  rpcbind
    100000    2   tcp    111  rpcbind
    100000    4   udp    111  rpcbind
    100000    3   udp    111  rpcbind
    100000    2   udp    111  rpcbind
    100000    4 local    111  rpcbind
    100000    3 local    111  rpcbind
    100000    2 local    111  rpcbind
    100007    2   udp   1011  ypbind
    100007    2   tcp   1023  ypbind
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100024    1   udp   1009  status
    100024    1   tcp   1021  status
    100021    0   udp   1008  nlockmgr
    100021    1   udp   1008  nlockmgr
    100021    3   udp   1008  nlockmgr
    100021    4   udp   1008  nlockmgr
    100021    0   tcp   1020  nlockmgr
    100021    1   tcp   1020  nlockmgr
    100021    3   tcp   1020  nlockmgr
    100021    4   tcp   1020  nlockmgr

On Tuesday 18 November 2003 02:47, Robert Watson wrote:
> On Mon, 17 Nov 2003, llx wrote:
> > i've a nfs server (FreeBSD 4.9) which exports the ports tree via NFS.
> >
> > on the client machine (FreeBSD 5.1) portupgrade fails:
> >  >  checking configure sumary... ERROR: No locking available. Running
> >  > Samba
> >
> >      would be unsafe
> >
> >  > configure: error: summary failure. Aborting config
> >
> > why does this happen? i thought that FreeBSD 5.x supports nfslocking as a
> > client. on the server is started rpc.lockd and rpc.statd (see output
> > rpcinfo below).
>
> Are you running rpc.statd and rpc.lockd on the client as well?
>
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> robert at fledge.watson.org      Network Associates Laboratories
>
> > cheers
> > llx
> >
> > ipcinfo -p <SERVER>
> >
> > sh-2.05b$ rpcinfo -p frigi
> >    program vers proto   port
> >     100000    2   tcp    111  portmapper
> >     100000    2   udp    111  portmapper
> >     100004    1   udp   1021  ypserv
> >     100004    2   udp   1021  ypserv
> >     100004    1   tcp   1023  ypserv
> >     100004    2   tcp   1023  ypserv
> >     100009    1   udp   1011  yppasswdd
> >     100009    1   tcp   1022  yppasswdd
> >     100005    3   udp   1008  mountd
> >     100005    3   tcp   1021  mountd
> >     100005    1   udp   1008  mountd
> >     100005    1   tcp   1021  mountd
> >     100003    2   udp   2049  nfs
> >     100003    3   udp   2049  nfs
> >     100003    2   tcp   2049  nfs
> >     100003    3   tcp   2049  nfs
> >     100021    1   udp    994  nlockmgr
> >     100021    3   udp    994  nlockmgr
> >     100021    4   udp    994  nlockmgr
> >     100021    1   tcp   1020  nlockmgr
> >     100021    3   tcp   1020  nlockmgr
> >     100021    4   tcp   1020  nlockmgr
> >     100024    1   udp    986  status
> >     100024    1   tcp   1019  status
> >
> > _______________________________________________
> > freebsd-stable at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"