Hi,

Eelco Dolstra <[EMAIL PROTECTED]>
writes:

> But as Marc pointed out, on a long-running system you still need to do that.  
> So
> you're better off cleaning /tmp from a cronjob.  Also, on a long-running 
> system,
> once you *do* reboot, the boot time increases a lot (on my laptop it took a 
> few
> minutes to delete /tmp).

Right, but don't forget the risks currently taken in the presence of
bind mounts under /tmp.

> In any case, the current command to delete it:
>
>   rm -rf --one-file-system /tmp/*
>
> is broken.  It will fail / do bad things if there are too many files or files
> starting with "-" in /tmp.  Better to do "find /tmp ... -print0 | xargs -0 rm 
> --
> ..." or something.

Right, but that's another story.

It looks to me that there's no compelling argument to leave `/tmp'
untouched across reboots.

Thanks,
Ludo'.

_______________________________________________
nix-dev mailing list
[email protected]
https://mail.cs.uu.nl/mailman/listinfo/nix-dev

Reply via email to