Hi,
I've been having trouble with my clamd build. When running clamd from
the command line the initial process never quits even after the
databases are loaded and fork is called. This causes init scripts to
stall.
The child runs, and is completely functional.
The parent process can be killed by
On Tue, 2004-11-02 at 20:11, Henri van Riel wrote:
> Hello Trog,
>
> Tuesday, November 2, 2004, 8:47:26 PM, you wrote:
>
> > On Tue, 2004-11-02 at 19:39, Henri van Riel wrote:
> > I'm just wondering why there are two processes...
>
> > They aren't processes, they are threads. Clamd spawns new th
Hello Trog,
Tuesday, November 2, 2004, 8:47:26 PM, you wrote:
> On Tue, 2004-11-02 at 19:39, Henri van Riel wrote:
> I'm just wondering why there are two processes...
> They aren't processes, they are threads. Clamd spawns new threads to do
> the actual work, and when a worker thread has been id
On Tue, 2004-11-02 at 19:39, Henri van Riel wrote:
> Hello all,
>
> I'm new to ClamAV and this list and I have the following `problem`.
>
> I use clamav together with p3scan but that is irrelevant to my
> question. I first start the clamd deamon and then the p3scan deamon.
> Everything starts jus
Hello all,
I'm new to ClamAV and this list and I have the following `problem`.
I use clamav together with p3scan but that is irrelevant to my
question. I first start the clamd deamon and then the p3scan deamon.
Everything starts just fine. But when I use clamdscan to scan a
directory for instance
