Date: Sun, 28 Aug 2022 10:42:13 +0200 (CEST) From: freebsd@oldach.net (Helge Oldach) To: Cy.Schubert@cschubert.com (Cy Schubert) Cc: otis@FreeBSD.org, freebsd@walstatt-de.de, grembo@freebsd.org, freebsd-current@freebsd.org, freebsd-ports@freebsd.org, yasu@freebsd.org Subject: Re: security/clamav: /ar/run on TMPFS renders the port broken by design Message-ID: <202208280842.27S8gDXn055868@nuc.oldach.net> In-Reply-To: <20220827082638.57901a72@slippy> from Cy Schubert at "27 Aug 2022 08:26:38"
next in thread | previous in thread | raw e-mail | index | archive | help
Cy Schubert wrote on Sat, 27 Aug 2022 17:26:38 +0200 (CEST): > As stated before in this thread, replacing /var/run with tmpfs is not a > supported configuration. Not supported? What is the purpose of /etc/rc.d/var then? That creates a tmpfs backed /var, populates it through mtree, and makes a proper /var/run available. However it doesn't (yet) create /var/run/clamav of course. It would be fairly easy to extend /etc/rc.d/var by a logic that walks through /usr/local/etc/mtree/* and runs mtree on each of the files found as needed. All that the security/clamav port would need to do then is to drop an appropriate small mtree file as /usr/local/etc/mtree/clamav. From a port's perspective that is the same logic as dropping service scripts as /usr/local/etc/rc.d/clamav-*. Kind regards Helge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202208280842.27S8gDXn055868>