unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 39708@debbugs.gnu.org
Subject: bug#39708: nfs-service-type broken: rpc.mountd respawns too quickly
Date: Sun, 08 Mar 2020 12:21:32 +0100	[thread overview]
Message-ID: <87r1y3ccsj.fsf@gnu.org> (raw)
In-Reply-To: <87lfob5rrm.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 08 Mar 2020 00:39:57 -0500")

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> OK, I've managed to find the problem.  rpc.mountd daemonizes itself upon
> starting by default, which is not supported by Shepherd (at least not
> its `make-forkexec-constructor' procedure).  I had to pass the
> '--foreground' option to workaround this limitation (c.f.: commit
> 5fdc5b2d57d2e7ab04dbaf9c85e7f34eebe81495).

Great!  (I had replied earlier before seeing this message.)

> It'd be interesting to see what systemd does when a service is hinted as
> forking in its configuration file.  We should also document that
> limitation in the Shepherd info manual (see attached patch for
> Shepherd).

Good idea.  I pushed a slightly different version as Shepherd commit
3bc4a9c96c76abf78c76d71d42536e62ea173b21.

Thanks,
Ludo’.

      reply	other threads:[~2020-03-08 11:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  3:58 bug#39708: nfs-service-type broken: rpc.mountd respawns too quickly Maxim Cournoyer
2020-02-22 11:05 ` Ludovic Courtès
2020-03-08  3:19   ` Maxim Cournoyer
2020-03-08  3:41   ` Maxim Cournoyer
2020-03-08  4:03     ` Maxim Cournoyer
2020-03-08  4:27       ` Maxim Cournoyer
2020-03-08 11:13       ` Ludovic Courtès
2020-03-08 14:37         ` Maxim Cournoyer
2020-03-08 14:43           ` Ludovic Courtès
2020-03-08 16:59             ` Ricardo Wurmus
2020-03-08 17:29               ` Maxim Cournoyer
2020-03-08  5:39   ` Maxim Cournoyer
2020-03-08 11:21     ` Ludovic Courtès [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

  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=87r1y3ccsj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39708@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).