| Summary: | Add a /etc/conf.d file for nfsmount to pass options to rpc.statd | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Cort (RETIRED) <tcort> |
| Component: | Current packages | Assignee: | Network Filesystems <net-fs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | CC: | jakub, tcort |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Thomas Cort (RETIRED)
2006-03-23 07:22:26 UTC
cat /etc/conf.d/nfs # /etc/conf.d/nfs # If you wish to set the port numbers for lockd, # please see /etc/sysctl.conf # Number of servers to be started up by default RPCNFSDCOUNT=8 # Options to pass to rpc.mountd # ex. RPCMOUNTDOPTS="-p 32767 RPCMOUNTDOPTS="" # Options to pass to rpc.statd # ex. RPCSTATDOPTS="-p 32765 -o 32766" RPCSTATDOPTS="" <------- HERE! # Options to pass to rpc.idmapd RPCIDMAPDOPTS="" # Options to pass to rpc.gssd RPCGSSDOPTS="" # Options to pass to rpc.svcgssd RPCSVCGSSDOPTS="" # Timeout (in seconds) for exportfs EXPORTFSTIMEOUT=30 This bug is about /etc/init.d/nfsmount not /etc/init.d/nfs. /etc/init.d/nfsmount doesn't use /etc/conf.d/nfs. (In reply to comment #2) > This bug is about /etc/init.d/nfsmount not /etc/init.d/nfs. > /etc/init.d/nfsmount doesn't use /etc/conf.d/nfs. Could you explain what kind of options are you going to pass to nfsmount? It's client, there's exactly nothing you could do w/ the NFS server deamons configuration from the client side. (In reply to comment #3) > (In reply to comment #2) > > This bug is about /etc/init.d/nfsmount not /etc/init.d/nfs. > > /etc/init.d/nfsmount doesn't use /etc/conf.d/nfs. > > Could you explain what kind of options are you going to pass to nfsmount? It's > client, there's exactly nothing you could do w/ the NFS server deamons > configuration from the client side. I have diskless clients, and on each client /var/lib/nfs is read-only while /var/local/lib/nfs is read-write. I want to configure rpc.statd (which is started in /etc/init.d/nfsmount) on the client to use a non-default state directory path. This involves passing the "-P /var/local/lib/nfs" option to rpc.statd. Well, I don't see why you need nfsmount for this. Honestly - I don't see why we to install this script at all... All I need for 100% working mount of NFS exported directories on the client side is this line: www.example.com:/usr/local/overlays /mnt/nfs/overlays nfs auto,user,ro,nolock,tcp,hard,intr,nfsvers=3 0 0 and NFS support in kernel. No nfs-mount run in any runlevel, no rcp* daemons running on client, portmap not running on client, nothing... That all with (properly set up) firewalls on both sides. So, I'd say we should kinda revisit this needless cruft. (In reply to comment #5) > No nfs-mount run in any runlevel, no rcp* daemons running on client, portmap > not running on client, nothing... That all with (properly set up) firewalls on > both sides. So, I'd say we should kinda revisit this needless cruft. In the setup here, a user has a home directory that gets automatically mounted when he/she logs in, and it gets automatically unmounted when he/she logs out. The server's /etc/exports looks like this... /diskless 10.1.32.0/24(ro,async,no_root_squash) /home/user0 10.1.32.0/24(rw,root_squash,sync) /home/user1 10.1.32.0/24(rw,root_squash,sync) ... The clients need rpc.statd running to do file locking. For instance, openoffice.org and eclipse need to lock files in the user's home directory. (In reply to comment #6) > The clients need rpc.statd running to do file locking. For instance, > openoffice.org and eclipse need to lock files in the user's home directory. Oo.org crashes badly w/ NFS here, locks or not - apparently OO.org bug I'd say. :) I don't need locks for anything else, so I just got rid of the locks and the daemons bloat as described above (there's a small mod needed in /etc/init.d/netmount so that netmount doesn't check for for portmap w/ nfs mounts). That's it. I see there can be legitimate need for such stuff, but it should IMHO be optional. With a bit of tweaking and proper setup, there's no need to run all those daemons for a lot of people (I especially hate the portmap thing). netmount init script does the job quite nicely. Just my (In reply to comment #6) > The clients need rpc.statd running to do file locking. For instance, > openoffice.org and eclipse need to lock files in the user's home directory. Oo.org crashes badly w/ NFS here, locks or not - apparently OO.org bug I'd say. :) I don't need locks for anything else, so I just got rid of the locks and the daemons bloat as described above (there's a small mod needed in /etc/init.d/netmount so that netmount doesn't check for for portmap w/ nfs mounts). That's it. I see there can be legitimate need for such stuff, but it should IMHO be optional. With a bit of tweaking and proper setup, there's no need to run all those daemons for a lot of people (I especially hate the portmap thing). netmount init script does the job quite nicely. Just my 0.02 :) |