GNU bug report logs - #45202
pcscd service doesn't respond to SIGTERM

Previous Next

Package: guix;

Reported by: Raffael Stocker <r.stocker <at> mnet-mail.de>

Date: Sat, 12 Dec 2020 19:24:01 UTC

Severity: normal

Done: Brice Waegeneire <brice <at> waegenei.re>

Bug is archived. No further changes may be made.

Full log


Message #40 received at 45202-done <at> debbugs.gnu.org (full text, mbox):

From: Brice Waegeneire <brice <at> waegenei.re>
To: Raffael Stocker <r.stocker <at> mnet-mail.de>
Cc: Tobias Geerinckx-Rice <me <at> tobias.gr>, 45202-done <at> debbugs.gnu.org
Subject: Re: bug#45202: pcscd service doesn't respond to SIGTERM
Date: Sat, 03 Jul 2021 20:25:39 +0200
Hello Raffael,

Raffael Stocker <r.stocker <at> 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




This bug report was last modified 3 years and 324 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.