[SOLVED] Systemd starts gpg-agent mysteriously and does not end it with the last login session

Alpha90 · 05-29-2014, 11:22 PM

I am running an up to date arch linux 3.14.4 box with systemd 212-3 and gnupg 2.0.22. I do not know how long this perticular problem has been going on but I was troubleshooting something else with a new test user and found out after I logged out and back into my regular user that my test user session did not fully close because gpg-agent was running. I have been trying to figure out for days what is causing it. I log in through a tty and gpg-agent is already started so X isnt starting it. So i searched through my bash files both system files and local user and found no reference to gpg-agent. I disabled /etc/profile.d/gpg-agent.sh thinking that might be the problem however that did not work. Since it was a process that was started right after logind I disabled all my daemons, rebooted, and logged into root and gpg-agent still was started. I restarted again into emergency mode this time to see if it would load and it didnt. So something must load into multi-user mode that does not into emergency. How ever I can not figure out what that something is.

So I am looking for maybe a lead in the right direction or a solution to fix this problem. The onlything close to a solution.

I found via google was adding pgrep gpg-agent|kill to .bash_logout which feels alittle to hackerish like ducktaping a problem instead of fixing it.

unSpawn · 05-30-2014, 01:56 AM

Quote:

Originally Posted by Alpha90

The onlything close to a solution. I found via google was adding pgrep gpg-agent|kill to .bash_logout which feels alittle to hackerish like ducktaping a problem instead of fixing it.

You're right about that.

Quote:

Originally Posted by Alpha90

(..) So something must load into multi-user mode that does not into emergency. How ever I can not figure out what that something is.

Couple of things to try: check its PPID and "walk the chain" of processes back. Find its PID and run a 'cat -v /proc/$PID/cmdline'. That could reveal switches to 'grep -r' directories for. (Not running Arch but so far stuff in /etc/kde/env and file /usr/bin/keychain matches and none of the systemd stuff.)

Alpha90 · 05-30-2014, 02:16 AM

Checking the PPID was a good idea and thank you for telling me how to do that but in this case it did not help the PPID is 1. Checking the switches just lead to an env file that listed tmp directories where socket are.

unSpawn · 05-30-2014, 12:18 PM

OK. Please post actual output of

Code:

\ps af -U $LOGNAME -opid,ppid,args --sort=pid # obfuscate or cut irrelevant parts
\ps --no-header -C gpg-agent -o pid|while read _PID; do strings -an1 /proc/$_PID/cmdline\
|sed -e "s|^-||g" -e "s|^-||g"|while read ARG; do [ "${ARG:0:1}" != "/" -a  ${#ARG} -gt 10 ] \
&& grep ${ARG} -r /etc/ /usr/ ; done; done

Alpha90 · 05-30-2014, 03:21 PM

Actually I figured it out. my bash profile was sourcing an shell file that had 644 permissions but somehow was executed anyway. Moving the script got rid of the problem but I still am not sure why gpg-agent did not close when my last login session ended.

unSpawn · 05-30-2014, 03:33 PM

No idea. Try killing it nicely (15) on exit before killing it good (9)?

Alpha90 · 05-30-2014, 04:00 PM

so i would need to just kill the daemon if I wanted it to exit when the session ends?