Date: Mon, 18 Nov 2019 23:44:17 -0800 From: Craig Leres <leres@freebsd.org> To: Kurt Jaeger <pi@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r517347 - in head: . security security/clamav security/clamav-milter security/clamav/files Message-ID: <5af5d0b9-4085-a921-3669-d2715c962fd9@freebsd.org> In-Reply-To: <204993e5-3226-b99b-a1bd-3cf96e9302e8@freebsd.org> References: <201911122007.xACK7Kog058578@repo.freebsd.org> <204993e5-3226-b99b-a1bd-3cf96e9302e8@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-11-18 16:07, Craig Leres wrote: > On 2019-11-12 12:07, Kurt Jaeger wrote: >> Author: pi >> Date: Tue Nov 12 20:07:20 2019 >> New Revision: 517347 >> URL:https://svnweb.freebsd.org/changeset/ports/517347 >> >> Log: >> security/clamav: upgrade 0.101.4 -> 0.102.0 > > Just in case anyone else runs into this issue: the 0.102.0 version of > freshclam dumps core when the current working directory is unreadable. I > run freshclam from cron using a wrapper script that posts nagios status > using send_nsca. This job started dumping core after upgrading to > 0.102.0. (The fix for me was to add a "cd /tmp" to the script). > > I filed this upstream bug report: > > https://bugzilla.clamav.net/show_bug.cgi?id=12442 And upstream reports that this issue will be fixed in a patch to 0.102 "shortly" Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5af5d0b9-4085-a921-3669-d2715c962fd9>