On Monday 21 March 2005 18:23, Isaac Clerencia wrote: > In this "kmail+gpg in gentoo" howto they just use: > killall gpg-agent
Thanks Isaac. Hmmm. That would kill any gpg-agent process the user running it is allowed to kill, not just the one that was started "in the same environment". (And return errors for any gpg-agent processes he's not allowed to...) I was hoping for a bit more controlled solution, but maybe that is something that needs to be worked on upstream... [EMAIL PROTECTED]:~$ su test Password: [EMAIL PROTECTED]:/home/fjp$ killall gpg-agent gpg-agent(3744): Operation not permitted gpg-agent: no process killed [EMAIL PROTECTED]:/home/fjp$ gpg-agent --daemon gpg-agent[10422]: Secure memory is not locked into core gpg-agent[10422]: directory `/home/test/.gnupg' created gpg-agent[10422]: directory `/home/test/.gnupg/private-keys-v1.d' created GPG_AGENT_INFO=/tmp/gpg-VqWlOk/S.gpg-agent:10423:1; export GPG_AGENT_INFO; [EMAIL PROTECTED]:/home/fjp$ killall gpg-agent gpg-agent(3744): Operation not permitted gpg-agent[10423]: SIGTERM received - shutting down ... gpg-agent[10423]: gpg-agent (GnuPG) 1.9.15 stopped [EMAIL PROTECTED]:/home/fjp$ exit exit [EMAIL PROTECTED]:~$ Cheers, FJP P.S. What is the "Secure memory is not locked into core" message about?
pgpQxYarVsM02.pgp
Description: PGP signature
