Date: Sat, 27 Aug 2022 15:27:25 +0200 From: Michael Gmelin <grembo@freebsd.org> To: freebsd@oldach.net Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org, yasu@freebsd.org, freebsd@walstatt-de.de Subject: Re: security/clamav: /ar/run on TMPFS renders the port broken by design Message-ID: <E3110EFB-EF59-40C3-ACBF-496C7F309B49@freebsd.org> In-Reply-To: <202208271318.27RDI9Jd044045@nuc.oldach.net> References: <202208271318.27RDI9Jd044045@nuc.oldach.net>
index | next in thread | previous in thread | raw e-mail
> On 27. Aug 2022, at 15:18, freebsd@oldach.net wrote: > > Michael Gmelin wrote on Sat, 27 Aug 2022 15:02:04 +0200 (CEST): >> (you're removing /var/run, which shouldn't be removed > > Not quite. It's actually not uncommon to boot with an empty /var. Please see /etc/rc.d/var and related. That’s a good point. > The request that ports/packages should consider this case is not exactly unreasonable IMO. > If I was the maintainer, I would simply add the code to create the directory for robustness sake (I for one deleted subdirs in /var/run more than once and would expect a port to fix this on restart, also to make sure correct permissions are applied). But since it doesn’t seem like this is going to happen, adding a custom rc file would be a viable short term workaround for the requester. I like the idea of having something like tmpfiles.d, it would also help port maintainers (could also be done as a port). Cheershelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E3110EFB-EF59-40C3-ACBF-496C7F309B49>