From: Raffael Stocker <r.stocker@mnet-mail.de>
To: 45202@debbugs.gnu.org
Subject: bug#45202: pcscd service (pcsc-lite) doesn't handle run directory properly
Date: Sat, 12 Dec 2020 15:31:22 +0100 [thread overview]
Message-ID: <87o8izhz9h.fsf@mnet-mail.de> (raw)
Hi,
I use the pcsc-lite package and noticed that the pcscd service is
sometimes not started by shepherd/herd. If it is started, "herd start
pcscd" gives me the following error message (sorry for the german part):
> herd: Ausnahmefehler während der Ausführung von »start« mit dem Dienst »pcscd«:
> In procedure open-file: No such file or directory: "/var/run/pcscd/pcscd.pid"
The reason seems to be that pcsc-lite creates its pid file in
"/run/pcscd/", but herd expects it in "/var/run/pcscd/". This leads to
the service not being started when the files in "/run/pcscd/" have not
been cleaned up (or so my interpretation). In this case, I get the
error message:
> herd: Ausnahmefehler während der Ausführung von »start« mit dem Dienst »pcscd«:
> Throw to key `%exception' with args `("#<&invoke-error program:
> \"/gnu/store/r1yd6czv3r0is0a1gfsrix3gslkba80v-pcsc-lite-1.9.0/sbin/pcscd\"
> arguments: () exit-status: 1 term-signal: #f stop-signal: #f>")'.
If I delete the "/run/pcscd" directory, the daemon will be started,
although with the first error message from above.
I have been using guix for only a week now and don't know how to edit
service definitions etc., but maybe someone more competent could have a
look at this.
Regards,
Raffael
next reply other threads:[~2020-12-12 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 14:31 Raffael Stocker [this message]
2020-12-12 22:18 ` bug#45202: pcscd service (pcsc-lite) doesn't handle run directory properly 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 ` 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=87o8izhz9h.fsf@mnet-mail.de \
--to=r.stocker@mnet-mail.de \
--cc=45202@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 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).