Date: Fri, 18 Nov 2022 11:28:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 267846] rc.conf: var_run_enable="YES" without any effect on tmpfs:/var/run Message-ID: <bug-267846-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267846 Bug ID: 267846 Summary: rc.conf: var_run_enable=3D"YES" without any effect on tmpfs:/var/run Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: conf Assignee: bugs@FreeBSD.org Reporter: ohartmann@walstatt.org Running CURRENT (FreeBSD 14.0-CURRENT #109 main-n259294-dc58b3fca5e7: Fri N= ov 18 09:26:42 CET 2022 amd64) and /var/run on tmpfs and having set=20 var_run_enable=3D"YES" (othervar_run_ tags untouched) in /etc/rc.conf seems not to have any influence whether tmpfs-based /var/run gets recovered in any way. One can easily checkout by installing port security/clamav and having /var/= run tmpfs backed. While up and running installing the port security/clamav results in a worki= ng port. Rebooting with the above settings in /etc/rc.conf[.local] leaves clam= av not working. By the way, /var/db is on non-volatile storage. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267846-227>