From: Martin Vaeth <martin@mvath.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Switching default tmpfiles and faster internet coming my way.
Date: Sun, 6 Dec 2020 07:55:29 -0000 (UTC) [thread overview]
Message-ID: <slrnrsp3k6.15nf8.martin@larch.invalid> (raw)
In-Reply-To: ccb1195c-72be-6fbc-342d-656ecada509b@gmail.com
Dale <rdalek1967@gmail.com> wrote:
>
> It sounds like a rather rare problem. Maybe even only during boot up.
It is a non-existent problem on openrc if you clean /tmp and /var/tmp
on boot (which you should do if you use opentmp):
The purpose of opentmpfiles is to fill these directories with
certain data during boot, and when run only during boot
(as it is supposed to be) there is nothing wrong with it.
The situation is different for systemd which runs tmpfiles
periodically to clean up data from /tmp and /var/tmp
(something which should argueably be done by a dedicated tool
instead of putting two different functionalities into the same
tool - the usual systemd misconception of trying to be monolithic).
There is a certain danger if you install a new package whose
ebuild processes on installation a certain tmpfiles.conf
which writes into one of the world-writable directories /tmp or
/var/tmp: Such an ebuild does an inherently unsafe thing during
installation (but it doesn't matter whether it does this using
opentmpfiles or by calling the shell commands manually), and I
would not hesitate to file a bug against such an ebuild.
next prev parent reply other threads:[~2020-12-06 7:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 1:40 [gentoo-user] Switching default tmpfiles and faster internet coming my way Dale
2020-12-04 2:06 ` Kusoneko
2020-12-04 7:44 ` Dale
2020-12-04 2:18 ` Michael Orlitzky
2020-12-04 2:22 ` Michael Orlitzky
2020-12-04 6:44 ` Dale
2020-12-04 14:23 ` Michael Orlitzky
2020-12-04 17:02 ` Dale
2020-12-05 13:43 ` Michael Orlitzky
2020-12-06 6:40 ` Dale
2020-12-04 10:47 ` Michael
2020-12-04 14:07 ` Michael Orlitzky
2020-12-04 8:55 ` tastytea
2020-12-04 14:07 ` Michael Orlitzky
2020-12-04 9:09 ` antlists
2020-12-04 10:06 ` Dale
2020-12-04 10:24 ` Michael
2020-12-07 4:24 ` Dale
2020-12-07 11:39 ` Wols Lists
2020-12-07 20:32 ` Dale
2020-12-06 7:55 ` Martin Vaeth [this message]
2020-12-06 10:45 ` [gentoo-user] " Michael
2020-12-06 12:37 ` Neil Bothwick
2020-12-06 12:53 ` Arve Barsnes
2020-12-06 12:54 ` Rich Freeman
2020-12-06 13:01 ` antlists
2020-12-06 13:45 ` Michael
2020-12-06 15:13 ` Rich Freeman
2020-12-06 16:25 ` Martin Vaeth
2020-12-06 12:55 ` antlists
2020-12-06 17:06 ` Martin Vaeth
2020-12-06 13:29 ` Michael Orlitzky
2020-12-06 16:57 ` Martin Vaeth
2020-12-06 21:44 ` Michael Orlitzky
2020-12-07 20:41 ` Martin Vaeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnrsp3k6.15nf8.martin@larch.invalid \
--to=martin@mvath.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox