From: Steve Dickson <SteveD@redhat.com>
To: Martin Pitt <martin.pitt@ubuntu.com>, linux-nfs@vger.kernel.org
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] [PATCH 0/2] some systemd unit changes
Date: Thu, 19 Mar 2015 14:20:01 -0400 [thread overview]
Message-ID: <550B1351.7080802@RedHat.com> (raw)
In-Reply-To: <1425403690-23847-1-git-send-email-martin.pitt@ubuntu.com>
On 03/03/2015 12:28 PM, Martin Pitt wrote:
> Hello NFS developers,
>
> reposting the two patches inline as requested by Steve.
>
> I'm currently systemd-ifying our nfs-utils Ubuntu package. For testing I put
> the NFS server and client (i. e. localhost:/foo/bar mounts) on the same
> machine. With that I get long hangs during shutdown on stopping the NFS .mount
> units, as when that happens the NFS server is already shut down.
>
> This is certainly a corner case as you'd usually not NFS-mount a share from
> localhost; but fixing it is relatively simple with the first patch, which makes
> sure that if NFS server and client are installed, the server starts before the
> client, and the client stops before the server.
>
> For a client without installed server this is harmless as Before= does not
> imply a dependency. Likewise, for an NFS server which does not mount shares by
> itself, it's also a no-op as remote-fs.target is empty. This would only
> slightly reorder the boot sequence for machines which both are an NFS server
> and have some remote NFS mounts, but I don't see an issue with that.
>
> The second patch make NFS start earlier in the boot (i. e. before
> basic.target), so that you can do things like put /var/ on NFS, or have rcS
> SysV init scripts which depend on $remote_fs work. I tested this on both a
> server and a client. This is certainly a bit more intrusive, but could be
> worthwhile; what do you think?
>
> Thanks for considering,
Committed....
steved.
>
> Martin
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
prev parent reply other threads:[~2015-03-19 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:28 [PATCH 0/2] some systemd unit changes Martin Pitt
2015-03-03 17:28 ` [PATCH 1/2] systemd: Order NFS server before client Martin Pitt
2015-03-03 17:58 ` [systemd-devel] " Zbigniew Jędrzejewski-Szmek
2015-03-03 17:28 ` [PATCH 2/2] systemd: Relax dependencies of services Martin Pitt
2015-03-03 18:08 ` [systemd-devel] " Zbigniew Jędrzejewski-Szmek
2015-03-03 20:12 ` Martin Pitt
2015-03-03 21:44 ` Steve Dickson
2015-03-19 18:20 ` Steve Dickson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=550B1351.7080802@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=systemd-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.