On 8/16/07, <b class="gmail_sendername">Orion Poplawski</b> &lt;<a href="mailto:orion@cora.nwra.com">orion@cora.nwra.com</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
NetworkManager is currently (in devel and F7) unusable with autofs and<br>NFS mounts.&nbsp;&nbsp;This is because NetworkManager is stopped very early in the<br>shutdown process (K02) and brings down the network with it.&nbsp;&nbsp;Then when<br>
autofs attempts to unmount any automounted nfs mounts, they fail because<br>the remote machine is not accessible.&nbsp;&nbsp;Eventually the machine hangs<br>trying to unmount the last nfs mounted directory.&nbsp;&nbsp;I suppose it might<br>timeout eventually, but it&#39;s beyond my patience to wait that long.
<br><br>Questions:<br><br>- Why is NetworkManager shutdown so early?<br><br>- Should autofs/nfs shutdown do a forced unmount if needed?&nbsp;&nbsp;Would that<br>work?<br><br>- Do we need tighter NIS/autofs integration into NetworkManager?
</blockquote><div><br>Moving forward&nbsp; we need much tighter integration with all NetworkManager and all<br>network services on the machine.&nbsp; What I have done to reduce contention as well<br>as boot time is to remove the following services from my init process
<br><br>iscsi<br>iscsid<br>ntpd<br>autofs<br>sshd<br>avahi-daemon<br>avahi-dnsconfd<br>yum-updatesd<br><br>They all now are started by custom scripts in /etc/NetworkManager/dispatcher.d.&nbsp; Yes<br>I know that theoretically autofs doesn&#39;t below there because it can mount non network
<br>drives, but I don&#39;t use that so it is there now.<br><br>I can pass some of my stuff along if you are interested.<br><br>Jon<br></div><br></div><br>