On 05/12/2013 04:34 PM, Anton Aylward wrote:
Go though the rest of the file system and look at directories that were CREATED many days ago that contain newly created files or at least files that were created long after the directories or the parent directory of those directories were.
Why should I check the content of directories that are not supposed to be in a directory that is cleaned automatically?
* Why? Are they taking up needed space?
They are filling /tmp thus making more difficult to visually look for files in /tmp. And I do not see why if they are not taking up needed space, then this should not be a problem. Are you saying that since they do not take up needed space, then it is OK to let them to fill [/var]/tmp without bounds?
First, what's this 'without bounds'?
Each boot/service start adds a new directory and currently there is no bound on the number of newly created directories, except for the number and size of files that the file system is able to contain.
Second, are they really taking up space? Try running 'df' and see if your /tmp is critical.
Each directory uses at least 4k, so they are taking space.
it sounds like this is an aesthetic argument, which is really unanswerable.
I see other 'junk' created in my /tmp from things like ssh, adobe, various caches, ssh and gpg, plugins to thunderbird, PPD files from CUPS (LOTS! of them!), email attachment files I've viewed, and more. All these are more significant than empty directories.
But they are removed automatically after 10 days.
Well, what about /var/spool/postfix? Under ./defer and ./deferred there are many directories and hopefully they are empty. Are you going to add those to your list of directories to delete? Why not? Oh, right, its not an aesthetic issue.
Is /var/spool/postfix expected to be cleaned automatically? No Are /tmp/systemd-private-* expected to be cleaned automatically? Yes, since /tmp was expected by upstream to be a tmpfs.
I wouldn't fiddle with the age of system created directories if I were you.
These directories are created by systemd when a service with PrivateTmp set to true is started. After a reboot, for sure a new one is created. Thus old directories are no more used by any process, hence it is safe to remove them.
Personally I think you're making a big issue of something that is going to go away anyway.
Ah, just wait and then no one is allowed to complain. Best, Andrea -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org