FS#15775 - [nfs-utils] start-statd is not valid /bin/sh script
Attached to Project:
Arch Linux
Opened by Dan McGee (toofishes) - Tuesday, 04 August 2009, 00:54 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 10 January 2010, 16:55 GMT
Opened by Dan McGee (toofishes) - Tuesday, 04 August 2009, 00:54 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 10 January 2010, 16:55 GMT
|
Details
When starting the netfs "daemon", you can see errors like
this when /bin/sh is linked to something other than bash:
$ sudo /etc/rc.d/netfs restart :: Unmounting Network Filesystems [DONE] :: Mounting Network Filesystems [BUSY] /bin/sh: Illegal option -p 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. [FAIL] This is due to the /usr/sbin/start-statd program having the opening line "#!/bin/sh -p", and -p is not a valid POSIX option. Do you guys know where to contact upstream and/or leave a bug report? The mailing list on sourceforge seems awfully full of spam. Anyway, as we patch this file in Arch to use conf.d, I've attached a working start-statd script that is fully sh-compatible. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Sunday, 10 January 2010, 16:55 GMT
Reason for closing: Fixed
Additional comments about closing: 1.2.1-3
Sunday, 10 January 2010, 16:55 GMT
Reason for closing: Fixed
Additional comments about closing: 1.2.1-3
[#1] http://repos.archlinux.org/viewvc.cgi/nfs-utils/repos/core-i686/start-statd.patch?view=co
dmcgee@galway ~
$ head -n1 /usr/sbin/start-statd
#!/bin/sh -p