Recommending '-o nolocks' incorrect, it is '-o nolock'
Bug #131789 reported by
Alex Howells
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: nfs-common
ahowells@
mount.nfs: rpc.statd is not running but is required for remote locking.
Either use '-o nolocks' to keep locks local, or start statd.
I know that rpc.statd isn't running and I *do* wish to use local locking, however I'm not going to get very far with '-o nolocks' as that is an invalid option; this needs to be updated to say "Either use '-o nolock' to keep locks local, or start statd.'
Keep up the great work guys :)
// Alex
Changed in nfs-utils: | |
importance: | Undecided → Low |
status: | New → Confirmed |
To post a comment you must log in.
Should probably be worth commenting that I'm running Gutsy on that laptop, and am not sure if the bug also affects Dapper / Feisty.