FS#15953 - [nfs-utils] SMNOTIFY_OPS from conf.d/nfs-common.conf ignored

Attached to Project: Arch Linux
Opened by Jim Pryor (Profjim) - Sunday, 16 August 2009, 14:08 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 10 January 2010, 16:56 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

If one follows the instructions supplied in the default /etc/conf.d/nfs-common.conf, one will add "--no-notify" to STATD_OPTS on the nfs server, and omit "--no-notify" from the STATD_OPTS on the nfs client. With the default configuration, NEED_STATD will also be blank, and so will be changed to "yes" by the /etc/rc.d/nfs-common script; hence statd and sm-notify will explicitly be run (on both server and client). However, if we've followed the instructions and omitted "--no-notify" on the client, then statd will itself launch sm-notify. Hence, we get a copy of sm-notify running on the client that ignores the user's SMNOTIFY_OPTS. (Will we also get a second copy of sm-notify running?)

Thread on forums: <http://bbs.archlinux.org/viewtopic.php?id=78137>

Additional info:
* package version(s): 1.2.0-3
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 10 January 2010, 16:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.2.1-3
Comment by Tobias Powalowski (tpowa) - Monday, 07 September 2009, 07:04 GMT
In adopted this from the aur packages, what exactly do you need?
The statd patch is wrong, anything else needs to be changed before releasing a new package?
Comment by Jim Pryor (Profjim) - Monday, 07 September 2009, 09:35 GMT
I think you're referring to  FS#15950 , correct?

With respect to the problem reported here, it seems that what's called for is some adjustment of the /etc/rc.d files, and corresponding documentation changes (the documentation consisting only of the comments in the /etc/conf.d files, AFAIK). I'm not sure I understand the nfs startup sequence well-enough to propose a specific fix. I can just see that the current documentation, together with the current rc.d script, are a bit screwy. Given the rc.d script, I can't understand why one would ever want to omit --no-notify from the STATD_OPTS?

Loading...