Hi Scott,
On 08.05.2015 14:23, Scott Kitterman wrote:
On May 8, 2015 7:43:14 AM EDT, Andreas Cadhalpun
andreas.cadhal...@googlemail.com wrote:
I wonder if the same happened in Ubuntu, which would explain the many
reports similar to #778507.
The reports stopped once we fixed the debconf
On May 8, 2015 7:43:14 AM EDT, Andreas Cadhalpun
andreas.cadhal...@googlemail.com wrote:
Hi Chris,
On 08.05.2015 03:39, Christoph Anton Mitterer wrote:
I'm reopening this for now, since it seems the fix didn't get applied
to
all installations of wheezy during upgrade to jessie.
AFAIU, part
Hi Chris,
On 08.05.2015 03:39, Christoph Anton Mitterer wrote:
I'm reopening this for now, since it seems the fix didn't get applied to
all installations of wheezy during upgrade to jessie.
AFAIU, part of the solution was to remove:
PidFile /var/run/clamav/freshclam.pid
from
On Fri, 2015-05-08 at 13:43 +0200, Andreas Cadhalpun wrote:
I see three ways forward:
a) Basically ignore the remaining cases and tell anyone who asks about
the warning that he can safely remove the PidFile setting.
b) Bump the version in the postinst check and hope it works this time.
Control: reopen -1
Hey.
I'm reopening this for now, since it seems the fix didn't get applied to
all installations of wheezy during upgrade to jessie.
AFAIU, part of the solution was to remove:
PidFile /var/run/clamav/freshclam.pid
from
/etc/clamav/freshclam.conf
which is done by the following
Control: tags -1 pending
Hi Milko,
On 18.01.2015 11:53, Milko Krachounov wrote:
On Friday, 30 October 2014 22:14:46 you wrote:
As this warning is completely harmless, when systemd is used, I don't
think it's worth to invest a lot of time trying to fix this.
It is not completely
On Friday, 30 October 2014 22:14:46 you wrote:
As this warning is completely harmless, when systemd is used, I don't
think it's worth to invest a lot of time trying to fix this.
It is not completely harmless---it breaks logrotate for me. Logrotate
fails to reload the daemon after rotating the
Package: clamav
Version: 0.98.5~rc1+dfsg-2
Severity: serious
The subject says it all. This may affect the ability of sysvinit to
start or stop the process (but I may be wrong), hence the serious severity.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Control: severity -1 normal
Hi Santiago,
On 30.10.2014 13:23, Santiago Vila wrote:
The subject says it all. This may affect the ability of sysvinit to
start or stop the process (but I may be wrong), hence the serious severity.
Clamav-freshclam works fine under sysvinit and thus I'm reducing
* Andreas Cadhalpun | 2014-10-30 17:20:55 [+0100]:
Hi Santiago,
Hi Andreas,
On 30.10.2014 13:23, Santiago Vila wrote:
The subject says it all. This may affect the ability of sysvinit to
start or stop the process (but I may be wrong), hence the serious severity.
In fact, this error message only
Hi Sebastian,
On 30.10.2014 21:55, Sebastian Andrzej Siewior wrote:
I don't get it.
Then let me try to explain it in more detail. ;)
Is systemd taking care of writing the PID file
No.
or is it not used at all?
It's not used, because freshclam is run in foreground mode, i.e. it
11 matches
Mail list logo
