Public bug reported:
After an upgrade from intrepid to jaunty, I installed nfs-common and
attempted to start the nfs-common service.
[EMAIL PROTECTED]:/var/log# /etc/init.d/nfs-common start
* Starting NFS common utilities
[fail]
/var/log/daemon.log had this error:
Dec 5 12:53:01 blumonc rpc.statd[10235]: Version 1.1.4 Starting
Dec 5 12:53:01 blumonc sm-notify[10236]: Already notifying clients; Exiting!
Dec 5 12:53:01 blumonc rpc.statd[10235]: unable to register (statd, 1, udp).
After making the following change to /etc/defaults/nfs-common, the nfs-
common init script succeeded:
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=no
[EMAIL PROTECTED]:/var/log# /etc/init.d/nfs-common start
* Starting NFS common utilities
[ OK ]
** Affects: nfs-utils (Ubuntu)
Importance: High
Status: New
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => High
--
[jaunty] nfs-common fails to start unless NEED_STATD=no
https://bugs.launchpad.net/bugs/305589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
