I'm not sure what's going on with the gpg-agent.service, but when i
reboot my computer, systemd hangs on it for 90 seconds (it "says"
1m30s anyways).
I can reproduce this in a session with `systemctl stop gpg-agent`
which hangs for about the same time.
In journald, we see this:
Jul 01 22:46:15 angela gpg-agent[5828]: scdaemon[5828]: DBG: SIGCONT received - breaking select
Jul 01 22:46:15 angela gpg-agent[5828]: scdaemon[5828]: SIGTERM received - shutting down ...
Jul 01 22:46:15 angela systemd[3858]: Stopping gpg-agent.service - GnuPG cryptographic agent and passphrase cache...
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: State 'stop-sigterm' timed out. Killing.
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Killing process 5825 (gpg-agent) with signal SIGKILL.
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Killing process 5828 (scdaemon) with signal SIGKILL.
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Killing process 5829 (pipe-connection) with signal SIGKILL.
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Killing process 5830 (gpg-agent) with signal SIGKILL.
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Killing process 5833 (gpg-agent) with signal SIGKILL.
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Main process exited, code=killed, status=9/KILL
Jul 01 22:47:45 angela systemd[3858]: gpg-agent.service: Failed with result 'timeout'.
Jul 01 22:47:45 angela systemd[3858]: Stopped gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
So on of two things:
1. gpg-agent should respect TERM signals better and/or;
2. the systemd unit should be less patient with it
a.