Lines Matching refs:var

2 title: Using /tmp/ and /var/tmp/ Safely
8 # Using `/tmp/` and `/var/tmp/` Safely
10 `/tmp/` and `/var/tmp/` are two world-writable directories Linux systems
16 1. `/tmp/` should be used for smaller, size-bounded files only; `/var/tmp/`
22 `/tmp/` nor `/var/tmp/` directly.
30 Note that `/tmp/` and `/var/tmp/` each define a common namespace shared by all
36 untrusted files. Hence: do not use guessable names in `/tmp/` or `/var/tmp/` —
56    (Linux; this doesn't bother with `/tmp/` or `/var/tmp/` at all, but uses the
62 `/var/tmp/` are replaced by private sub-directories, implemented through Linux
64 view `/tmp/` and `/var/tmp/` look and behave like they normally do, but in
66 `/var/tmp/`, and thus not system-wide locations anymore, but service-specific
73 `/tmp/` and `/var/tmp/`. When this option is used, the per-service temporary
77 `/var/tmp/` for sharing files and directories. If this option is turned on this
84 and directories stored in `/tmp/` and `/var/tmp/`. This means that files that
89 those in `/var/tmp` after 30 days.
114 3. �� Operate below a sub-directory of `/tmp/` and `/var/tmp/` you created, and
148 6. Don't use `/tmp/` or `/var/tmp/`, but use your own sub-directory under
150    unprivileged), or `/var/lib/` and `~/.config/` (similar, but with
152    `/tmp/` and `/var/tmp/` come with the implicit clean-up semantics described
193 Generally, files allocated from `/tmp/` and `/var/tmp/` are allocated from a
195 generally more restricted than `/var/tmp/`. This means, that in particular in
202 Some setups employ per-user quota on `/var/tmp/` and possibly `/tmp/`, to make
210 Both `/tmp/` and `/var/tmp/` are not necessarily available during early boot,