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

Previous Next

Full log

Message #22 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Raffael Stocker <r.stocker <at> mnet-mail.de>
Cc: bug-guix <at> gnu.org, 45202 <at> debbugs.gnu.org
Subject: Re: bug#45202: pcscd service (pcsc-lite) doesn't handle run
 directory properly
Date: Sun, 13 Dec 2020 12:49:27 +0100

[Message part 1 (text/plain, inline)]

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

[signature.asc (application/pgp-signature, inline)]

Previous Next

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