On Tue, Nov 18, 2014 at 7:43 AM, Theo de Raadt dera...@cvs.openbsd.org wrote:
/var/tmp has been changed to be a symlink to /tmp. Traditionally,
the difference between /tmp and /var/tmp has been that the former is
cleaned after a reboot, while the latter isn't. Making /var/tmp a
symlink
On 2014-11-18 Tue 12:58 PM |, Martin Schr??der wrote:
See hier(7):
A symbolic link to the system /tmp directory. To protect other users
of /var from overfill conditions, this is no longer a space you can
trust to retain storage over a reboot. Periodically cleaned by
daily(8).
My
/var/tmp has been changed to be a symlink to /tmp. Traditionally,
the difference between /tmp and /var/tmp has been that the former is
cleaned after a reboot, while the latter isn't. Making /var/tmp a
symlink to /tmp means it's no longer practical to make /tmp a ramdisk.
Is this a wise
2014-11-18 12:08 GMT+01:00 Liviu Daia liviu.d...@gmail.com:
/var/tmp has been changed to be a symlink to /tmp. Traditionally,
the difference between /tmp and /var/tmp has been that the former is
cleaned after a reboot, while the latter isn't. Making /var/tmp a
symlink to /tmp means it's
/var/tmp has been changed to be a symlink to /tmp. Traditionally,
the difference between /tmp and /var/tmp has been that the former is
cleaned after a reboot, while the latter isn't. Making /var/tmp a
symlink to /tmp means it's no longer practical to make /tmp a ramdisk.
Is this a wise
