On Tue, 1 Mar 2011 02:41, da...@systemoverlord.com said:
Other than on systems where $HOME is on a filesystem that does not
support sockets (e.g., NFS/CIFS/etc.), is anyone aware of an issue with
the use of --use-standard-socket? Seems like it would make restarting
GnuPG 2.1 will use
Daniel Kahn Gillmor wrote:
On 02/28/2011 06:49 PM, David Tomaschik wrote:
Each process has its own copy of the environment inherited from its
parent, so it's not possible to change the GPG_AGENT_INFO variable for
all processes. You could start gpg-agent with --use-standard-socket,
and
Hi,
I use a OpenPGP smartcard with gnupg 2.0.14 and Ubuntu for different
tasks. From time to time I face the following problem: The gpg-agent
crashes for some reason after entering the PIN, 'ps' reports the daemon
process as a zombie
STAT START TIME COMMAND
Zs Feb26 0:01 [gpg-agent]
On 02/28/2011 06:17 PM, Marco Steinacher wrote:
Hi,
I use a OpenPGP smartcard with gnupg 2.0.14 and Ubuntu for different
tasks. From time to time I face the following problem: The gpg-agent
crashes for some reason after entering the PIN, 'ps' reports the daemon
process as a zombie
STAT
On 02/28/2011 06:49 PM, David Tomaschik wrote:
Each process has its own copy of the environment inherited from its
parent, so it's not possible to change the GPG_AGENT_INFO variable for
all processes. You could start gpg-agent with --use-standard-socket,
and programs should fall back to that.
On 02/28/2011 08:20 PM, Daniel Kahn Gillmor wrote:
On 02/28/2011 06:49 PM, David Tomaschik wrote:
Each process has its own copy of the environment inherited from its
parent, so it's not possible to change the GPG_AGENT_INFO variable for
all processes. You could start gpg-agent with
On 02/28/2011 08:41 PM, David Tomaschik wrote:
Other than on systems where $HOME is on a filesystem that does not
support sockets (e.g., NFS/CIFS/etc.), is anyone aware of an issue with
the use of --use-standard-socket? Seems like it would make restarting
GPG an easier task.
I occasionally
