From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 43257@debbugs.gnu.org
Subject: [bug#43257] [PATCH] services: nfs: Require file-systems to be mounted before starting NFS shepherd service.
Date: Thu, 10 Sep 2020 09:42:58 +0200 [thread overview]
Message-ID: <87wo12jcvx.fsf@gnu.org> (raw)
In-Reply-To: <20200909121313.321a18d5@scratchpost.org> (Danny Milosavljevic's message of "Wed, 9 Sep 2020 12:13:22 +0200")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Wed, 09 Sep 2020 10:27:30 +0200
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Why do we need all of ‘file-systems’ rather than just the state file
>> systems?
>
> It really depends on what one uses it for, but for me it's this use case:
>
> * I have an extra hard drive that contains things I want to serve via
> NFS (it has nothing to do with the root file system).
> * The extra hard drive has to be mounted when NFS service starts up,
> otherwise exportfs errors out:
> If I don't require "file-systems", even if that drive is listed in the
> operating-system's file-systems list, it won't be mounted in time.
Oh, I see.
> I ran into this problem when merging Stefan's
> new "nfs-root-fs" system test into gnu/tests/nfs.scm .
>
> Does this make sense or is it the wrong solution?
I just realized that these services should just all depend on
‘user-processes’ (which depends on ‘file-systems’). So you should
probably just do that.
You can double-check with ‘guix system shepherd-graph’ that the
dependency graph looks good.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-09-10 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 16:47 [bug#43257] [PATCH] services: nfs: Require file-systems to be mounted before starting NFS shepherd service Danny Milosavljevic
2020-09-09 8:27 ` Ludovic Courtès
2020-09-09 10:13 ` Danny Milosavljevic
2020-09-10 7:42 ` Ludovic Courtès [this message]
2020-09-10 13:20 ` Danny Milosavljevic
2020-09-11 7:02 ` Ludovic Courtès
2020-09-11 8:23 ` Danny Milosavljevic
2020-09-11 14:47 ` Ludovic Courtès
2020-09-11 17:50 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo12jcvx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43257@debbugs.gnu.org \
--cc=dannym@scratchpost.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).