Re: Problems with nfs and Fedora 10 x86_64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I found that is I put

all:		127.0.0.1       in /etc/hosts.allow

mounting nfs partitions on the new server worked.

On Feb 2, 2009, at 1:01 PM, Margaret Doll wrote:

I am used to using portmap with nfs. Where is the documentation on the new rpcbind programs used on Fedora 10?

When I try to mount a partition across the network on the new system, I am getting

mount /numbers1 mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd.

netstat -nlp | grep LISTEN | grep -v LISTENING
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2082/rpcbind tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 4501/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2648/cupsd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2580/sendmail: acce tcp 0 0 ::: 111 :::* LISTEN 2082/rpcbind tcp 0 0 ::: 22 :::* LISTEN 4501/sshd

When I try to mount one of the new system's partition on an older system, the older system
says that the nfs server is not working.


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux