Date: Sat, 27 Aug 2022 11:21:40 +0200 From: Michael Gmelin <grembo@freebsd.org> To: FreeBSD User <freebsd@walstatt-de.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org>, yasu@freebsd.org Subject: Re: security/clamav: /ar/run on TMPFS renders the port broken by design Message-ID: <BEF532F0-FF5C-4BA9-859A-885E35F1B8E8@freebsd.org> In-Reply-To: <20220827083042.73e7f439@thor.intern.walstatt.dynvpn.de> References: <20220827083042.73e7f439@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27. Aug 2022, at 08:31, FreeBSD User <freebsd@walstatt-de.de> wrote: >=20 > =EF=BB=BFHello, >=20 > I'm referencing to Bug 259699 [2] and Bug 259585 [1]. >=20 > Port security/clamav is without doubt for many of FreeBSD users an importa= nt piece of security > software so I assume a widespread usage. >=20 > It is also a not uncommon use case to use NanoBSD or any kind of low-memor= y-footprint > installation schemes in which /var/run - amongst other system folders - ar= e created at boot > time as TMPFS and highly volatile. >=20 > In our case, the boxes running a small security appliance based upon FreeB= SD is rebooted every > 24 hours and so /var/run is vanishing. >=20 > To make the long story short: >=20 > The solution for this problem would be a check for existence and take acti= on addendum in > precmd() routine of the rc-script as sketched in Bug 259699. > The maintainer rejects such a workaround by arguing this would violate POL= A (see comment 4 in > PR 259699 [2]. The maintainer's argument regaring to mtree's files are sou= nd to me. >=20 > The question is: how can this issue be solved? >=20 > It is really hard to always chenge our local repository and patch whenever= clamav has been > patched and modified for what reason ever. >=20 > Tahanks for reading, >=20 Why don=E2=80=99t you simply add an rc script to your appliance that creates= the missing directory/directories on boot before clamav is started? Best Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BEF532F0-FF5C-4BA9-859A-885E35F1B8E8>