Your message dated Sun, 20 Aug 2017 19:09:26 +0200
with message-id <20170820170924.nyi6qoaunhm5u...@breakpoint.cc>
and subject line Re: Bug#830482: [Pkg-clamav-devel] Bug#830482: Fresh
installation causes freshclam to to fail
has caused the Debian Bug report #830482,
regarding clamav-freshclam: duplicate logging with systemd
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
830482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav-freshclam
Version: 0.99.2+dfsg-0+deb8u1
Severity: normal
Dear Maintainer,
freshclam is configured to log to its logfile by itself (UpdateLogFile).
However systemd unit file (as shipped with jessie) runs freshclam in
foreground and redirects its stdout to syslog.
This causes the log to go both to configured UpdateLogFile and to
/var/log/syslog.
Don't know if freshclam prints anything useful to stdout which isn't also in
logfile. If not, then maybe configure systemd unit to ignore stdout and
redirect only stderr to syslog.
-- Package-specific info:
--- configuration ---
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package
DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
#LogRotate true
LogTime true
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 30
ReceiveTimeout 30
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
SafeBrowsing yes
Bytecode true
#NotifyClamd /etc/clamav/clamd.conf
# Check for new database 24 times a day
Checks 48
DatabaseMirror clamav.mojhosting.sk
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
--- data dir ---
lrwxrwxrwx 1 root root 32 Jun 23 22:56 /var/lib/clamav ->
/var/spool/vscan/var/lib/clamav/
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages clamav-freshclam depends on:
ii clamav-base 0.99.2+dfsg-0+deb8u1
ii debconf [debconf-2.0] 1.5.56
ii dpkg 1.17.27
ii init-system-helpers 1.22
ii libc6 2.19-18+deb8u4
ii libclamav7 0.99.2+dfsg-0+deb8u1
ii libssl1.0.0 1.0.1t-1+deb8u2
ii logrotate 3.8.7-1+b1
ii lsb-base 4.1+Debian13+nmu1
ii procps 2:3.3.9-9
ii ucf 3.0030
ii zlib1g 1:1.2.8.dfsg-2+b1
clamav-freshclam recommends no packages.
Versions of packages clamav-freshclam suggests:
pn apparmor <none>
pn clamav-docs <none>
-- debconf information:
clamav-freshclam/update_interval: 24
clamav-freshclam/SafeBrowsing: false
clamav-freshclam/internet_interface:
clamav-freshclam/autoupdate_freshclam: daemon
clamav-freshclam/http_proxy:
clamav-freshclam/local_mirror: db.local.clamav.net
clamav-freshclam/NotifyClamd: true
clamav-freshclam/LogRotate: true
clamav-freshclam/proxy_user:
clamav-freshclam/PrivateMirror:
clamav-freshclam/Bytecode: true
--- End Message ---
--- Begin Message ---
On 2017-05-05 23:43:14 [+0200], To T. Joseph Carter wrote:
> On 2017-05-04 22:11:02 [+0200], To T. Joseph Carter wrote:
> > I will try to reproduce this myself over the weekend. The original
> > reported never came back to me. Just for the record: You run stable or
> > testing? And all you did was just a plain install? And you do have
> > systemd as default.
>
> You replied that you were using `sid' but didn't Cc the bug so here I
> add this detail for the protocol.
>
> All you say is that once you have the "UpdateLogFile" entry then
> freshclam won't work. Then you remove that line (or add # in front of
> it) and it works. So this is something I can't reproduce. It worked
> well here.
> What is the error message that you face?
no feedback, can't reproduce, closing.
Sebastian
--- End Message ---
_______________________________________________
Pkg-clamav-devel mailing list
Pkg-clamav-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
