~/.cache/keyring-* directories
by henca from LinuxQuestions.org on (#6D07E)
I have a Slackware 14.2 system with the home directory on a local HD. In my home directory on that machine I have:
Code: ls -ald ~/.cache/keyring-*
drwx------ 2 henca users 4096 Apr 29 2022 /home/henca/.cache/keyring-0ETEL1/
drwx------ 2 henca users 4096 Jul 29 2019 /home/henca/.cache/keyring-97894Z/
drwx------ 2 henca users 4096 May 11 18:50 /home/henca/.cache/keyring-E70M41/
drwx------ 2 henca users 4096 Sep 8 2022 /home/henca/.cache/keyring-HY7AS1/
drwx------ 2 henca users 4096 Aug 9 2019 /home/henca/.cache/keyring-IVVR5Z/
drwx------ 2 henca users 4096 Mar 23 18:43 /home/henca/.cache/keyring-KLL811/Each of those directories contain a socket named "control". It seems to me that a process named gnome-keyring-daemon creates these and at an uncontrolled shutdown like a power outage it leaves old stuff behind and next time starts on a new directory. This is no big deal.
However, in another environment, with more machines running different versions of Slackware with shared home directories on NFS I have hundreds of thousands of ~/.cache/keyring-* directories. Most of those directories are empty. It seems as if most of those directories were created after Slackware 15.0 was introduced. My theory is, that even after a clean shutdown or logout of Slackware 15.0 the gnome-keyring-daemon cleans up the ~/.cache/keyring-*/control socket but leaves the empty directory ~/.cache/keyring-* behind and next time started creates yet another new directory. However, I haven't logged out or shut down hundreds of thousands of times the last year, somehow gnome-keyring might restart by itself or have some other reason to start with a new directory.
With hundreds of thousands of empty directories in each users home directory and each empty directory requiring 4kB of storage this is becoming more of an issue.
What would break if I simply removed the gnome-keyring package from the Slackware 15.0 machines?
With home directories on NFS it is tricky to use a tool like lsof to see which files or directories are still in use, some other machine in the network could be using files. Also, I don't like the idea of a solution like a cron job run by root which deletes files and directories in users home directories.
regards Henrik
Code: ls -ald ~/.cache/keyring-*
drwx------ 2 henca users 4096 Apr 29 2022 /home/henca/.cache/keyring-0ETEL1/
drwx------ 2 henca users 4096 Jul 29 2019 /home/henca/.cache/keyring-97894Z/
drwx------ 2 henca users 4096 May 11 18:50 /home/henca/.cache/keyring-E70M41/
drwx------ 2 henca users 4096 Sep 8 2022 /home/henca/.cache/keyring-HY7AS1/
drwx------ 2 henca users 4096 Aug 9 2019 /home/henca/.cache/keyring-IVVR5Z/
drwx------ 2 henca users 4096 Mar 23 18:43 /home/henca/.cache/keyring-KLL811/Each of those directories contain a socket named "control". It seems to me that a process named gnome-keyring-daemon creates these and at an uncontrolled shutdown like a power outage it leaves old stuff behind and next time starts on a new directory. This is no big deal.
However, in another environment, with more machines running different versions of Slackware with shared home directories on NFS I have hundreds of thousands of ~/.cache/keyring-* directories. Most of those directories are empty. It seems as if most of those directories were created after Slackware 15.0 was introduced. My theory is, that even after a clean shutdown or logout of Slackware 15.0 the gnome-keyring-daemon cleans up the ~/.cache/keyring-*/control socket but leaves the empty directory ~/.cache/keyring-* behind and next time started creates yet another new directory. However, I haven't logged out or shut down hundreds of thousands of times the last year, somehow gnome-keyring might restart by itself or have some other reason to start with a new directory.
With hundreds of thousands of empty directories in each users home directory and each empty directory requiring 4kB of storage this is becoming more of an issue.
What would break if I simply removed the gnome-keyring package from the Slackware 15.0 machines?
With home directories on NFS it is tricky to use a tool like lsof to see which files or directories are still in use, some other machine in the network could be using files. Also, I don't like the idea of a solution like a cron job run by root which deletes files and directories in users home directories.
regards Henrik