On Tuesday 30 January 2007 14:22, Bo Ørsted Andresen wrote: > On Monday 29 January 2007 20:12:22 Alan McKinnon wrote: > > Why not just keep it as /var/tmp? Defined as: > > > > "The /var/tmp directory is made available for programs that require > > temporary files or directories that are preserved between system > > reboots. Therefore, data stored in /var/tmp is more persistent than > > data in /tmp. > > "Files and directories located in /var/tmp must not be deleted when > > the system is booted. Although data stored in /var/tmp is typically > > deleted in a site-specific manner, it is recommended that deletions > > occur at a less frequent interval than /tmp." > > > > Strictly per the standard, /var/tmp is the correct place for emerge > > temp files and /tmp is incorrect. Not that it matters on your box > > with your symlink (which is totally standard-compliant btw) > > Why would PORTAGE_TMPDIR be required to or in any way benefit from > surviving reboots?
It doesn't, and that's not why it defaults to /var/tmp If you read FHS, you see that /tmp is intended for scratch pad stuff - when the process exits, it has no further need for it's tmp files left behind and they are liable for "garbage collection". So /tmp is unsuitable for PORTAGE_TMPDIR per the standard. /var/tmp is also for temp files, with the added feature that a reboot will not cause them to be deleted i.e. they are long lived. /var/tmp exceeds the requirements for PORTAGE_TMPDIR so it is an ideal place. These temp files are "deleted in a site-specific manner" so portage is free to dictate exactly how this will happen. The word "reboot" is in the definition as a characteristic of /var/tmp but has nothing to do with the reason why it's chosen for PORTAGE_TMPDIR alan -- gentoo-user@gentoo.org mailing list
