all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: Raffael Stocker <r.stocker@mnet-mail.de>
Cc: 45202-done@debbugs.gnu.org
Subject: bug#45202: pcscd service doesn't respond to SIGTERM
Date: Sat, 03 Jul 2021 20:25:39 +0200	[thread overview]
Message-ID: <87v95rcl0c.fsf_-_@waegenei.re> (raw)
In-Reply-To: <87k0tlvsns.fsf@mnet-mail.de> (Raffael Stocker's message of "Mon,  14 Dec 2020 06:54:47 +0100")

Hello Raffael,

Raffael Stocker <r.stocker@mnet-mail.de> writes:

> Interesting indeed.  From looking at the source of pcsc-lite (main() in
> pcscdaemon.c) it seems it's not modifying its sigmask.  IIRC, child
> processes inherit the parent's ignored signals, so if shepherd is
> ignoring SIGTERM before a fork() and not resetting to default before an
> exec(), pcscd will never receive the SIGTERM.  This might explain the
> behaviour.  I have not checked shepherd's source to confirm.
>
> If this is so, it should probably be fixed in shepherd, right?

Thank yu for the analysis of the issue, it helped me a lot to fix it.
The sheperd pcscd serice wasn't using the correct procedure to start the
daemon, it is fixed in e789ce538ed848bacb8f4eb5742f78b965ccf57c.

Cheers,
- Brice




      reply	other threads:[~2021-07-03 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 14:31 bug#45202: pcscd service (pcsc-lite) doesn't handle run directory properly Raffael Stocker
2020-12-12 22:18 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-12-13  0:33   ` Raffael Stocker
2020-12-13 11:49     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-12-14  5:54       ` Raffael Stocker
2021-07-03 18:25         ` Brice Waegeneire [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v95rcl0c.fsf_-_@waegenei.re \
    --to=brice@waegenei.re \
    --cc=45202-done@debbugs.gnu.org \
    --cc=r.stocker@mnet-mail.de \
    /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.