Recommending '-o nolocks' incorrect, it is '-o nolock'

Bug #131789 reported by Alex Howells
2
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: nfs-common

ahowells@prometheus:/media/collie$ sudo mount -t nfs collie.0wn3d.us:/helios helios/
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

Revision history for this message
Alex Howells (howells) wrote :

Should probably be worth commenting that I'm running Gutsy on that laptop, and am not sure if the bug also affects Dapper / Feisty.

Timo Aaltonen (tjaalton)
Changed in nfs-utils:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nfs-utils - 1:1.1.2-2ubuntu1

---------------
nfs-utils (1:1.1.2-2ubuntu1) hardy; urgency=low

  * New upstream version (LP: #131789, #208021)
  * Merge from Debian unstable, remaining changes:
    - Change the Maintainer address.
    - Adjust initscripts version dependancy.

 -- Timo Aaltonen <email address hidden> Tue, 01 Apr 2008 18:02:05 +0300

Changed in nfs-utils:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.