From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Raffael Stocker <r.stocker@mnet-mail.de>
Cc: 45202@debbugs.gnu.org
Subject: bug#45202: pcscd service (pcsc-lite) doesn't handle run directory properly
Date: Sun, 13 Dec 2020 12:49:27 +0100 [thread overview]
Message-ID: <87a6uij588.fsf@nckx> (raw)
In-Reply-To: <87im96o881.fsf@mnet-mail.de>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Raffael,
Raffael Stocker 写道：
> However, I now noticed a new one: pcscd doesn't seem to be
> killable
> easily (at least not by a TERM signal), so "herd stop pcscd" has
> no effect. Sending a KILL signal and starting with "herd start
> pcscd"
> works without problems, though.
I can reproduce this. Interestingly(?) it only affects the pcscd
started by Shepherd.
Manual $(guix build pcsc-lite)/sbin/pcscd invocations, both with
and without --foreground, are eminently killable with TERM alone.
The Shepherd's instance hangs at
strace: Process 11441 attached
select(7, [6], NULL, NULL, NULL
with no activity at all when signal 15 is delivered. I don't know
any tricks to attach faster to get more leading context.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-13 11:54 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 [this message]
2020-12-14 5:54 ` Raffael Stocker
2021-07-03 18:25 ` bug#45202: pcscd service doesn't respond to SIGTERM Brice Waegeneire
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=87a6uij588.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=45202@debbugs.gnu.org \
--cc=me@tobias.gr \
--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 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).