Date: Sat, 30 Dec 2017 13:31:58 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224728] security/clamav: Fails to start when /var/run is on volatile TEMPFS Message-ID: <bug-224728-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224728 Bug ID: 224728 Summary: security/clamav: Fails to start when /var/run is on volatile TEMPFS Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ler@FreeBSD.org Reporter: ohartmann@walstatt.org Assignee: ler@FreeBSD.org Flags: maintainer-feedback?(ler@FreeBSD.org) Created attachment 189219 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D189219&action= =3Dedit Makefile and rc-script patches security/clamav doesn not restart after the initial installation, once the system has been repbooted and the /var/run folder resides on tempfs or memo= ry filesystem. The reason seems to be the loss of the /var/run/clamav folder, which is initially installed when the package/port gets the first time installed, but the appropriate rc script doesn't check for the existence of /var/run/clamav. The result is shown bewlow. Attached I'll offer some ideas for a patch of the port framework to aim for= the problem, see attachment. [...] service clamav-clamd restart clamav_clamd not running? Starting clamav_clamd. ERROR: LOCAL: Socket file /var/run/clamav/clamd.sock could not be bound: No such file or directory Closing the main socket. ERROR: Can't unlink the socket file /var/run/clamav/clamd.sock /usr/local/etc/rc.d/clamav-clamd: WARNING: failed to start clamav_clamd Kind regards, O. Hartmann --=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-224728-13>