From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5733C1382C5 for ; Sun, 6 Dec 2020 07:55:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2D182E0919; Sun, 6 Dec 2020 07:55:37 +0000 (UTC) Received: from ciao.gmane.io (static.214.254.202.116.clients.your-server.de [116.202.254.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C6B19E08FB for ; Sun, 6 Dec 2020 07:55:36 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1klotK-0006Za-Qz for gentoo-user@lists.gentoo.org; Sun, 06 Dec 2020 08:55:34 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Martin Vaeth Subject: [gentoo-user] Re: Switching default tmpfiles and faster internet coming my way. Date: Sun, 6 Dec 2020 07:55:29 -0000 (UTC) Message-ID: References: User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: cf70f2f3-6279-4df1-ae87-89885ad369c3 X-Archives-Hash: 763ed59a529bd0b7ac40f5e9a0351374 Dale 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.