I looked into this issue a bit more, and it looks like all I needed to do is remove the /var/run/network/mountnfs lock directory to get it working again. Either there was a bad version sometime that didn't clean it up or something crashed or killed it before it could remove the directory, but it seems to work fine now.<br>
<br><div class="gmail_quote">On Mon, Jan 10, 2011 at 11:04 PM, Aaron Barany <span dir="ltr"><<a href="mailto:akb825@gmail.com">akb825@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This bug is still present in the version of initscripts that migrated to Testing today.<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Tue, Jan 4, 2011 at 9:58 PM, Michael Biebl <span dir="ltr"><<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">reassign 608862 initscripts<br>
thanks<br>
<div><br>
On 05.01.2011 05:58, Aaron Barany wrote:<br>
> The following was printed in the syslog: "if-up.d/mountnfs[wlan1]:<br>
> if-up.d/mountnfs[wlan1]: lock /var/run/network/mountnfs exist, not mounting"<br>
> When looking through /etc/network/if-up.d/mountnfs, tries to mkdir<br>
> /var/run/network/mountnfs and prints this error if that fails.<br>
><br>
> On a somewhat related note, I noticed that /etc/network/if-up.d/mountnfs has<br>
> mixed spaces and tabs, as well as general inconsistency with indent levels.<br>
<br>
</div>Not a network-manager problem as it seems.<br>
Re-assigning to the package, shipping /etc/network/if-up.d/mountnfs<br>
<div><br>
<br>
<br>
> On Tue, Jan 4, 2011 at 11:23 AM, Michael Biebl <<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>> wrote:<br>
><br>
>> tags 608862 moreinfo<br>
>> thanks<br>
>><br>
>> On 04.01.2011 06:37, Aaron Barany wrote:<br>
>>> Package: network-manager<br>
>>> Version: 0.8.1-6<br>
>>> Severity: normal<br>
>>><br>
>>> I have a couple nfs volumes set to automount via fstab, and previously<br>
>> they<br>
>>> would automatically mount when network-manager connected to my wireless<br>
>>> network. However, since updating to the latest version of network-manager<br>
>> it<br>
>>> will no longer mount the volumes when the wireless network connects,<br>
>> forcing me<br>
>>> to mount those volumes manually.<br>
>><br>
>> network-manager is not responsible for mounting nfs volumes.<br>
>><br>
>> All it does is run /etc/NetworkManager/dispatcher.d/01ifupdown on<br>
>> connection<br>
>> changes.<br>
>> 01ifupdown then runs the hooks in /etc/network/if-*.d/<br>
>><br>
>> Please add debugging calls to 01ifupdown so you can check if the script is<br>
>> executed correctly.<br>
>><br>
>> This should help you find out what is going wrong.<br>
>><br>
>> If you have this information, please attach it to the bug report.<br>
>><br>
<br>
<br>
<br>
</div>--<br>
<div><div></div><div>Why is it that all of the instruments seeking intelligent life in the<br>
universe are pointed away from Earth?<br>
<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>