| 1 |
antlists <antlists@××××××××××××.uk> wrote: |
| 2 |
> On 06/12/2020 07:55, Martin Vaeth wrote: |
| 3 |
>> Dale<rdalek1967@×××××.com> wrote: |
| 4 |
>>> It sounds like a rather rare problem. Maybe even only during boot up. |
| 5 |
> |
| 6 |
>> It is a non-existent problem on openrc if you clean /tmp and /var/tmp |
| 7 |
>> on boot (which you should do if you use opentmp): |
| 8 |
> |
| 9 |
> Which breaks a lot of STANDARDS-COMPLIANT software. |
| 10 |
|
| 11 |
Actually, /var/tmp needs not be cleaned at boot to be on the safe side: |
| 12 |
|
| 13 |
grep /var/tmp /usr/lib/tmpfiles.d/* |
| 14 |
/usr/lib/tmpfiles.d/portage-ccache.conf:x /var/tmp/ccache |
| 15 |
/usr/lib/tmpfiles.d/systemd-tmp.conf:x /var/tmp/systemd-private-%b-* |
| 16 |
/usr/lib/tmpfiles.d/systemd-tmp.conf:X /var/tmp/systemd-private-%b-*/tmp |
| 17 |
/usr/lib/tmpfiles.d/systemd-tmp.conf:R! /var/tmp/systemd-private-* |
| 18 |
/usr/lib/tmpfiles.d/tmp.conf:q /var/tmp 1777 root root 30d |
| 19 |
|
| 20 |
The q entry is irrelevant for the intended usage of opentmpfiles, |
| 21 |
and the others cannot be exploited. |
Archives