From: Martin Castillo <castilma@uni-bremen.de>
To: 30993@debbugs.gnu.org
Subject: bug#30993: OpenSSH sshd killed by Shepherd 0.4.0
Date: Tue, 1 May 2018 15:13:05 +0200 [thread overview]
Message-ID: <a61fd87e-8f57-bae7-7747-e4be02161a4d@uni-bremen.de> (raw)
In-Reply-To: <20180406124101.GB1883@jasmine.lan>
(resending because I forgot to CC the list)
On 06.04.2018 14:41, Leo Famulari wrote:
>> Hmm, where could that SIGTERM come from? ‘make-kill-destructor’ uses it
>> when a service is stopped, and otherwise it’s sent when we’re shutting
>> the system down. But here?…
>
> Indeed, that is the question. Does anyone have advice for debugging?
>
> I still have this issue and so I'm continuing to use Shepherd 0.3.2.
>
Maybe one could somehow strace herd, or change the make-kill-destructor
to log every time it is being executed?
I'm not that fluent in guile so maybe someone else could do that?
next prev parent reply other threads:[~2018-05-01 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 20:08 bug#30993: OpenSSH sshd killed by Shepherd 0.4.0 Leo Famulari
2018-04-06 8:21 ` Ludovic Courtès
2018-04-06 12:41 ` Leo Famulari
2018-04-06 14:37 ` Ludovic Courtès
2018-05-01 13:13 ` Martin Castillo [this message]
2018-05-01 20:43 ` Ludovic Courtès
2018-05-03 15:16 ` Martin Castillo
2018-05-03 16:38 ` Leo Famulari
2018-05-04 2:01 ` Martin Castillo
2018-05-06 19:50 ` Leo Famulari
2018-05-07 19:10 ` Martin Castillo
2018-07-19 13:15 ` bug#32197: " Clément Lassieur
2018-07-19 14:26 ` Clément Lassieur
2018-07-19 16:57 ` Leo Famulari
2018-07-23 17:08 ` Martin Castillo
2018-08-28 9:47 ` Ludovic Courtès
2018-11-17 9:46 ` bug#30993: issue: ssh-daemon could not be started Taegil Bae
2018-11-19 21:22 ` Ludovic Courtès
2018-11-20 1:33 ` Taegil Bae
2019-05-14 13:33 ` bug#30993: OpenSSH sshd killed by Shepherd 0.4.0 Ludovic Courtès
2019-05-14 18:21 ` Leo Famulari
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=a61fd87e-8f57-bae7-7747-e4be02161a4d@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=30993@debbugs.gnu.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 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.