Your message dated Sun, 7 May 2006 14:23:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#366310: freshclam's crontab causes benign mail to root 
with error
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: clamav
Version: 0.88.2-1
Severity: normal

        Hi,

 "clamav" is pulled by "sylpheed-claws-clamav" (which is pulled by
 sylpheed-claws-plugins) on my system, hence I end up with
 clamav-freshclam, but not with clamav-daemon.

 Each time /etc/cron.d/clamav-freshclam is run, it will read
 /etc/clamav/clamd.conf and reload the daemon via the configured
 LocalSocket.  Since I don't have the daemon, I don't have the
 /var/run/clamav/clamd.ctl socket, and it fails, hence the mail.

 Please make sure that freshclam doesn't try to update the daemon when
 it isn't installed.  For example:
 - move the the config file to the dameon package (this is probably the
   hardest with the compatibility hacks in place, and it won't cover
   cases where the dameon package is removed but not purged)
 - test for the presence of the dameon's binary on the system prior to
   trying to open the socket in freshclam (ugly)
 - shell snipset that tests for the daemon's presence in the crontab


   Bye,

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages clamav depends on:
ii  clamav-freshclam [clamav-data 0.88.2-1   downloads clamav virus databases f
ii  libc6                         2.3.6-7    GNU C Library: Shared libraries
ii  libclamav1                    0.88.2-1   virus scanner library
ii  zlib1g                        1:1.2.3-11 compression library - runtime

Versions of packages clamav recommends:
ii  arj                           3.10.22-2  archiver for .arj files
ii  unzoo                         4.4-4      zoo archive extractor

-- no debconf information

-- 
Loïc Minier <[EMAIL PROTECTED]>
"You can gtk_main_run, but you can't gtk_widget_hide." --danw, 19-jul-04


--- End Message ---
--- Begin Message ---
On Sun, May 07, 2006, Stephen Gran wrote:
> Specifying a single binary check loses the ability to have freshclam
> notify an out of band clamd in this way.

 I agree with that.

> I am not sure I understand you here.  At any rate, freshclam does not
> support reading an alternate config file.

 What I meant was to use the current freshclam.conf as a template to a
 real freshclam.conf which would be generated depending on the existence
 of the clamd daemon on the system.

> It seems reasonable on the face of it, but again, I don't immediately
> see a way to know which clamd to check for.  If you can think of that, I
> will implement it.

 No, I can't think of anyway to do that, as clamd can be in /opt or
 whatever, and it might be useful to report that the socket does not
 exist, or is not connected.

 I understand your desire to support this mode of operation, and can not
 think of any way of supporting my desire of robustness while being
 flexible enough to permit out of the Debian packages clamd
 installations.

 Hence, I'm closing my bug, thanks for the discussion!

-- 
Loïc Minier <[EMAIL PROTECTED]>

--- End Message ---

Reply via email to