On Thu, Jul 28, 2016 at 06:34:55PM -0500, Rex Dieter wrote:
> David A. De Graaf wrote:
>
> > systemd and autofs/nfs are at war and have been ever since systemd
> > appeared.
> >
> > Specifically, if machine A has an open connection to machine B
> > and B goes down or become inaccessible, then A cannot shutdown.
> > A's shutdown sequence hangs, waiting for B to respond to an unmount
> > command, which will not/cannot happen.
>
> Like this bug?
> https://bugzilla.redhat.com/show_bug.cgi?id=1359423
>
> -- Rex
No, not really. That BZ claims that merely having an nfs mount
active will cause a slow shutdown.
In my experience, if the nfs connection is working properly, ie,
the network is still connected, the server is still working and
responsive, then shutdown is not delayed.
Only when the remote machine fails to respond is the nfs umount
command blocked. It then waits for a response that will not and
cannot come. That's what's dumb.
--
David A. De Graaf DATIX, Inc. Hendersonville, NC
d...@datix.us www.datix.us
"Flint must be an extremely wealthy town: I see that each of you
bought two or three seats."
-Victor Borge, playing to a half-filled house in Flint, Mich.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
