From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 39708@debbugs.gnu.org
Subject: bug#39708: nfs-service-type broken: rpc.mountd respawns too quickly
Date: Sun, 08 Mar 2020 13:29:34 -0400 [thread overview]
Message-ID: <87a74q69hd.fsf@gmail.com> (raw)
In-Reply-To: <87y2saok8y.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 08 Mar 2020 17:59:41 +0100")
Hello Ricardo!
Ricardo Wurmus <rekado@elephly.net> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>>
>>>> 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’.
>>>
>>> That process doesn't create a PID file, so that doesn't work.
>>
>> OK, so ‘--foreground’ was the right thing. Thanks for explaining!
>
> Does this affect the system test at all? When I added nfs-service-type
> I also added a system test, which passed. Did I miss something?
As I mentioned in an earlier message in this thread;
> Even with 'herd status rpc.mountd' reporting that it is stopped and
> disabled, and 'pidof rpc.mountd' showing 6 processes, the NFS service
> manages to work, at least for the very limited testing I've done.
So, the test validating that files written to the mounted NFS share
appear in the exported file system would pass, but if you view the
output of 'herd status nfs' on a system configured before the fix you'd
see rpc.mountd reported as stopped and disabled (with something like 6
processes running :-)).
Maxim
next prev parent reply other threads:[~2020-03-08 17:30 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a74q69hd.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=39708@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.