on boot, statd don't start without nfs in /etc/fstab

Bug #578992 reported by Pascal Grudler
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nfs-common

But I use NFS filesystem via automount (autofs5). And this not works without rpc.statd.

I think it's a problem in the upstart job configuration :

root@s19096l:/etc# head -7 init/statd.conf
# statd - NSM status monitor

description "NSM status monitor"
author "Steve Langasek <email address hidden>"

start on (started portmap or mounting TYPE=nfs)
stop on stopping portmap

After I manually launch "start statd", all work well.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue May 11 22:56:59 2010
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nfs-utils

Revision history for this message
Pascal Grudler (pascal-grudler) wrote :
Revision history for this message
Gerb (g.roest) wrote :

Changing /etc/init/statd.conf to read the "start" line like this:

start on ((started portmap and local-filesystems) or mounting TYPE=nfs)

worked for me (no nfs in /etc/fstab but only with automount, and /var in separate filesystem)

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.