Thomas Trepl wrote: > Please have a look to the attached patch on the nfsutils.xml to > address most of Randys points. I don't think we should mention tcpwrappers in the required dependencies section. It is really only a library in this context and, as pointed out, only needed by tcpwrappers.
Better would be: tcpwrappers Configuration If you enabled support for tcpwrappers (required by portmap) by creating /etc/hosts.deny, ensure you have an entry in the /etc/hosts.allow file for access from the portmap daemon that overrides any rules in the /etc/hosts.deny file. See the man page in section 5 for hosts_access for details on creating appropriate rules. > The "nfsmount" thing is still open. I think this from the very past > and that program doesn't exist anylonger. The question is, what is > start-statd good for and who calls it? Well, the man page for rpc.statd says: For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/sm. When starting, it normally runs sm-notify to iterate through these files and notify the peer rpc.statd on those machines. But I will note that on my systems /var/lib/nfs/sm is empty for both the client and server even though I do have an nfs entry mounted. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
