Mandi! Hugo Lefeuvre
In chel di` si favelave...
> thanks for your time. I have done some more tests myself and went ahead
> with the upload, I hope everything will be fine now. Sorry for the trouble.
I canconfirm that now the bug is solved.
Thanks!
--
dott. Marco Gaiarin
Thank you. You're very welcome. Regards,
Filipe
On 14/10/19 08:20, Hugo Lefeuvre wrote:
Hi Filipe, Sebastian,
I could only test from 0.100.0+dfsg-0+deb8u1 as I couldn't find
0.100.3+dfsg-0+deb8u1 anywhere in the archives and I'm out of servers
running clamav-daemon 0.100.3+dfsg-0+deb8u1; but
Hi Filipe, Sebastian,
> I could only test from 0.100.0+dfsg-0+deb8u1 as I couldn't find
> 0.100.3+dfsg-0+deb8u1 anywhere in the archives and I'm out of servers
> running clamav-daemon 0.100.3+dfsg-0+deb8u1; but as /run/clamav/ is root
> owned in 0.100.0+dfsg-0+deb8u1 and clamav-daemon
Hello,
I could only test from 0.100.0+dfsg-0+deb8u1 as I couldn't find
0.100.3+dfsg-0+deb8u1 anywhere in the archives and I'm out of servers
running clamav-daemon 0.100.3+dfsg-0+deb8u1; but as /run/clamav/ is root
owned in 0.100.0+dfsg-0+deb8u1 and clamav-daemon 0.101.4+dfsg-0+deb8u2
got
Hi Hugo,
On Sun, 13 Oct 2019 10:25:37 +0200 Hugo Lefeuvre wrote:>
> I have prepared a regression update addressing this issue. It would be a
> true benefit for the quality of this upload if somebody could give it
a try
> before I go on with uploading. You can find (UNRELEASED) amd64 builds,
>
Hello,
I can test it but probably only in half a day time or so. I'll get back to
you then. Many thanks.
Regards,
Filipe
On October 13, 2019 09:33:17 Hugo Lefeuvre wrote:
Hi Filipe,
I did strike this in three boxes. Straight upgrade but opted not to touch
config when asked. Don't know
On 10/12/19 6:32 PM, Hugo Lefeuvre wrote:
> Hi,
>
> I did not notice this bug during my tests. I have just tried to reproduce
> it by upgrading a jessie system from 0.100.3+dfsg-0+deb8u1 to
> 0.101.4+dfsg-0+deb8u1 and did not experience any issue restarting
> clamav-daemon.
>
> Furthermore,
Hi Filipe,
> I did strike this in three boxes. Straight upgrade but opted not to touch
> config when asked. Don't know if it matters. However I did not find any
> reference to /etc/systemd/system/clamav-daemon.service.d/extend.conf in the
> package scripts as in stretch.
>
> The chown did make
Hello,
I did strike this in three boxes. Straight upgrade but opted not to touch
config when asked. Don't know if it matters. However I did not find any
reference to /etc/systemd/system/clamav-daemon.service.d/extend.conf in the
package scripts as in stretch.
The chown did make the
Hi,
I did not notice this bug during my tests. I have just tried to reproduce
it by upgrading a jessie system from 0.100.3+dfsg-0+deb8u1 to
0.101.4+dfsg-0+deb8u1 and did not experience any issue restarting
clamav-daemon.
Furthermore, /var/run/clamav/ belonging to root:root or clamav:root does
Hello,
Using /etc/systemd/system/clamav-daemon.service.d/extend.conf
[Service]
ExecStartPre=-/bin/mkdir /run/clamav
ExecStartPre=/bin/chown clamav /run/clamav
from stretch works for me.
I would prefer
[Service]
ExecStartPre=/bin/mkdir -p /run/clamav
ExecStartPre=/bin/chown clamav /run/clamav
Package: clamav-daemon
Version: 0.101.4+dfsg-0+deb8u1
Severity: normal
Dear Maintainer,
I've just upgraded ClamAV on jessie, but clamav does not restart. On log i
get:
Oct 11 09:02:40 ibrsamba clamd[28918]: Fri Oct 11 09:02:40 2019 -> !LOCAL:
Socket file /var/run/clamav/clamd.ctl could not
12 matches
Mail list logo
