Temporary lock files?

Daniel Kahn Gillmor dkg at fifthhorseman.net
Tue Sep 8 20:19:26 CEST 2015

On Tue 2015-09-08 12:26:11 -0400, Werner Koch wrote:
> On Wed, 12 Aug 2015 19:57, aslam at mythicflow.com said:
>> My ~/.gnupg directory is getting filled with files named like
>> ".#lk0x7feb6a637540.<hostname>.26914".
>> Shouldn't these get deleted automagically?
> It used to be common prectise to have a cron job deleting ".#" prefixed
> files after a few days.  I don't know wether current distros install
> such a cron job.

I don't know of any such cronjob in debian.  Would you expect this to be
something system-wide, or run on a per-user basis?

for lockfiles that are relevant only to the running system (as this
would seem to be, since it has the hostname in it), the usual place
these would go on a modern distro is $XDG_RUNTIME_DIR (typically
/run/user/1000 for a user with numeric id 1000).  These directories are
ephemeral, involve no disk access for filesystem modifications, and are
automatically cleaned up upon restart.

Should we be changing the default location of the lockfiles on modern
linux/unix distributions of GnuPG?

For home directories accessed on multiple machines simultaneously
(e.g. NFS-mounted homedirs), are the locks required to work across


More information about the Gnupg-users mailing list