Great Scott, I will treat this as a error message (warning) that is suppressed. Are you able to confirm exactly what clamav-daemon can be used for is this better to set up or leave clamav running as a daemon by default: what benefit does it have over using clamav.
On Mon, Feb 4, 2019 at 7:51 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the clamav package: > > #921400: ClamAV tosses error on notifications > > It has been closed by Scott Kitterman <deb...@kitterman.com>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Scott Kitterman < > deb...@kitterman.com> by > replying to this email. > > > -- > 921400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921400 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Scott Kitterman <deb...@kitterman.com> > To: 921400-d...@bugs.debian.org > Cc: > Bcc: > Date: Mon, 04 Feb 2019 21:47:04 -0500 > Subject: Re: [Pkg-clamav-devel] Bug#921400: ClamAV tosses error on > notifications > On Monday, February 04, 2019 07:06:37 PM Brian Holaday wrote: > > Package: clamav > > Version: 0.100.2+dfsg-0+deb9u1 > > Severity: normal > > > > Step #1: Run Update > > # sudo freshclam > > > > Step #2: Error is shown: > > "Clamd was NOT notified: Can't connect to clamd through > > /var/run/clamav/clamd.ctl: No such file or directory" > > > > Looking at a fix looks like it may be this: > > # clamav is dependent of clamav-daemon > > > > I have yet to test this however to see if the issue resolves itself : > seems > > like on a fresh install this happens. > > None of this is a bug. > > In Debian, freshclam is configured to run as a daemon. You do not need to > run > it manually. In any case, all the 'error' means is that clamd isn't > running. > If you haven't either installed clamav-daemon or you've stopped it, then > that's normal. > > Scott K > > > ---------- Forwarded message ---------- > From: Brian Holaday <br...@codemonkeyrawks.net> > To: sub...@bugs.debian.org > Cc: > Bcc: > Date: Mon, 4 Feb 2019 19:06:37 -0700 > Subject: ClamAV tosses error on notifications > Package: clamav > Version: 0.100.2+dfsg-0+deb9u1 > Severity: normal > > Step #1: Run Update > # sudo freshclam > > Step #2: Error is shown: > "Clamd was NOT notified: Can't connect to clamd through > /var/run/clamav/clamd.ctl: No such file or directory" > > Looking at a fix looks like it may be this: > # clamav is dependent of clamav-daemon > > I have yet to test this however to see if the issue resolves itself : > seems like on a fresh install this happens. > >