When Does NFS Get Enabled At Boot?

[Tim Daneliuk]

On 06/10/2013 07:45 PM, Tom H wrote:
> On Mon, Jun 10, 2013 at 8:43 PM, Tom H <tomh0665 at gmail.com> wrote:
>> On Mon, Jun 10, 2013 at 3:51 PM, Tim Daneliuk <tundra at tundraware.com> wrote:
>>> On 06/10/2013 01:43 PM, Tom H wrote:
>>>> On Sun, Jun 9, 2013 at 12:59 PM, Tim Daneliuk <tundra at tundraware.com>
>>>> wrote:
>>>>>
>>>>> On 13.04 I can mount NFS shares from the command line no problem, but if
>>>>> I
>>>>> try to do it at boot time from fstab, the system hangs and says it is
>>>>> waiting for idmapd and statd to start.
>>>>
>>>>
>>>> Try adding "_netdev" to the fstab options of the nfs mounts. They'll
>>>> be attempted after the network's up; and hopefully after rpc.idmapd is
>>>> started. (rpc.statd isn't used by/needed for nfs4.)
>>>>
>>>> I'm using nfs and not nfs4 on Ubuntu but AFAIK there's an upstart job
>>>> to ensure that idmapd is started before an nfs4 mount is attempted.
>>>> You might want to file a bug report against this job if its "start on
>>>> ..." statement isn't starting it when it's meant to.
>>>
>>> Thanks, I'll look into this. As a matter of interest, where are
>>> the upstart job definitions found? Are they plain text editable?
>>
>> You're welcome.
>>
>> They're text files in "/etc/init".
>
> It's best to override a job rather than edit it directly.
>
> cp /etc/init/<job>.conf /etc/init/<job>.override
> vi /etc/init/<job>.override
>


OK so adding _netdev to the mount options does not fix this.

I think a bug report is in order only ... I'm not sure
where/how Ubuntu likes this done (I am more of a FreeBSD
and CentOS/RHEL person).  Could some kind soul point me
to the right place to file the bug?

Thanks

-- 
-----------------------------------------------------------------------
Tim Daneliuk