Bug#867877: clamav-daemon: please respect manual configuration

2017-08-30 Thread Sebastian Andrzej Siewior
On 2017-08-21 15:22:49 [+0200], Luca Capello wrote: > Hi there, Hi, > Given that no documentation was available, not even in the upstream > files, I was lost, so this would be the first improvement. > > I was not aware that upstream chose the "full-systemd path", so I guess > changing that is a

Bug#867877: clamav-daemon: please respect manual configuration

2017-08-21 Thread Luca Capello
severity 867877 minor tags 867877 + upstream thanks Hi there, On Sun, 20 Aug 2017 19:08:15 +0200, Sebastian Andrzej Siewior wrote: > On 2017-07-10 23:39:53 [+0200], To Luca Capello wrote: > > On 2017-07-10 11:40:20 [+0200], Luca Capello wrote: > > > while debugging why the TCP socket was not

Bug#867877: clamav-daemon: please respect manual configuration

2017-08-20 Thread Sebastian Andrzej Siewior
On 2017-07-10 23:39:53 [+0200], To Luca Capello wrote: > On 2017-07-10 11:40:20 [+0200], Luca Capello wrote: > > Hi there, > Hi, > > > while debugging why the TCP socket was not responding, I discovered that > > everything was fine if clamd was manually started via the CLI. And then > > I found

Bug#867877: clamav-daemon: please respect manual configuration

2017-07-10 Thread Sebastian Andrzej Siewior
On 2017-07-10 11:40:20 [+0200], Luca Capello wrote: > Hi there, Hi, > while debugging why the TCP socket was not responding, I discovered that > everything was fine if clamd was manually started via the CLI. And then > I found . > > Please, this is becoming

Bug#867877: clamav-daemon: please respect manual configuration

2017-07-10 Thread Luca Capello
Package: clamav-daemon Version: 0.99.2+dfsg-0+deb8u2 Severity: important User: product...@infomaniak.com Usertags: infomaniak.com-virus Hi there, while debugging why the TCP socket was not responding, I discovered that everything was fine if clamd was manually started via the CLI. And then I