From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58859) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fozqB-0005Sx-9M for guix-patches@gnu.org; Sun, 12 Aug 2018 19:32:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fozq6-0002Ky-CL for guix-patches@gnu.org; Sun, 12 Aug 2018 19:32:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:44099) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fozq6-0002Kt-7r for guix-patches@gnu.org; Sun, 12 Aug 2018 19:32:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fozq5-0001vm-Ui for guix-patches@gnu.org; Sun, 12 Aug 2018 19:32:01 -0400 Subject: [bug#32358] Add pcscd service Resent-Message-ID: References: <87a7q2lqc6.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me> <87zhxu7lr9.fsf@gmail.com> <87sh3jkyqg.fsf@gmail.com> From: =?UTF-8?Q?Cl=C3=A9ment?= Lassieur In-reply-to: <87sh3jkyqg.fsf@gmail.com> Date: Mon, 13 Aug 2018 01:31:44 +0200 Message-ID: <878t5b6u1r.fsf@lassieur.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Chris Marusich Cc: 32358@debbugs.gnu.org Hi all! Chris Marusich writes: > Hi Arun, > > It turns out that when we run pcscd in the foreground with the -f > option, it won't emit messages to syslog. Instead, it emits messages to > stderr, and those messages will not be stored in logs, as explained in > the following bug report: > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D30939 > > To ensure users can easily find the messages, I think we should avoid > using the "-f" option. > > In addition, pcscd logs its PID to /var/run/pcscd/pcscd.pid. To ensure > that Shepherd can still tell if the service is alive even when we do not > run it in the foreground, we should invoke make-forkexec-constructor > with the #:pid-file keyword argument. Without the '-f' option, pcscd would return immediately, and thus calling MAKE-FORKEXEC-CONSTRUCTOR wouldn't make sense. Instead, you could just INVOKE it. See the 'prosody', 'postgres' and 'nginx' services for examples. And you could stop it by sending SIGTERM to the PID in /var/run/pcscd/pcscd.pid I guess. Also, the systemd unit files I've seen use the '--auto-exit' and '--hotplug' options. Do you know if they make sense for us? Cl=C3=A9ment