On 12/01/14 16:38, Maxim Khitrov wrote:
> On Tue, Nov 18, 2014 at 7:43 AM, Theo de Raadt
> 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.
On Tue, Nov 18, 2014 at 7:43 AM, Theo de Raadt 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 to /tmp means it'
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 w
2014-11-18 12:08 GMT+01:00 Liviu Daia :
> /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 practic
/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 change
