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:13:41 +0100	[thread overview]
Message-ID: <87y2sbcd5m.fsf@gnu.org> (raw)
In-Reply-To: <87tv2z5w7z.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 07 Mar 2020 23:03:44 -0500")

Hi!

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

> I think I've gathered a clue!

[...]

> scheme@(shepherd service)> (make-forkexec-constructor
>   (list "/gnu/store/qyz1bncxlkxv44c03sva2akfsyqzkzh5-nfs-utils-2.4.2/sbin/rpc.mountd" "--debug" "all"))
> $5 = #<procedure 7f67f82862a0 at shepherd/service.scm:930:8 args>
> scheme@(shepherd service)> ($5)
> $6 = 816
> scheme@(shepherd service)> (system "pidof rpc.mountd")
> warning: 'waitpid' -1 failed unexpectedly: No child processes
> 817

So that means that rpc.mountd “daemonizes”.  Thus, shepherd shouldn’t
look at the PID of the process it spawns, but rather at what
rpc.mountd’s PID file contains (I assume it creates a PID file,
right?).  IOW, we need to pass #:pid-file to ‘make-forkexec-constructor’.

Does that work for you?

Thanks for debugging!

Ludo’.

  parent reply	other threads:[~2020-03-08 11:14 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 [this message]
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

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=87y2sbcd5m.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).