Jerry Bell said:
> It appears this was the case. I knew it was going to be something so
> completely simple that I would be shamed from the list for a while, but I
> was so far in the forest, I couldn't see the trees anymore.
Fehh - like we all haven't been there before. Have a beer on me -
hopef
It appears this was the case. I knew it was going to be something so
completely simple that I would be shamed from the list for a while, but I
was so far in the forest, I couldn't see the trees anymore.
BTW, I have no idea how that happened. I am pretty diligent about
shutting things down before
>
> René Berber wanted us to know:
>
> >I agree with this, the log shows two different processes running, both
> >as daemon.
> >Could the start script run freshclam twice?
>
> No, when he upgraded from 0.81 to 0.83, it looks like the old process
> was never killed. It happily kept running.
> -
> >
> > Could the start script run freshclam twice?
>
> Or could /usr/local/etc/rc.d/ contain two differently named
> startup scripts? That would do it, too. :)
>
> - Mark
Lacking any other problem, one of the two has to launch an earlier version
of the tool in order to generate the error shown
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> René Berber
> Sent: woensdag 9 maart 2005 23:52
> To: clamav-users@lists.clamav.net
> Subject: [Clamav-users] Re: Two persistent problems with clamav
>
>
> I agre
René Berber wanted us to know:
>I agree with this, the log shows two different processes running, both
>as daemon.
>Could the start script run freshclam twice?
No, when he upgraded from 0.81 to 0.83, it looks like the old process
was never killed. It happily kept running.
--
Regards...
Freddie Cash wrote:
[snip]
Looking at the log output, it looks like you have two separate processes
running. One that wakes up every 30 minutes at 22 after and 52 after.
The other that wakes up at half-past (at least, there's not enough log
output to confirm the pattern). The entries are very
On March 9, 2005 01:33 pm, Jerry Bell wrote:
> > How do you start freshclam, as daemon or manually to test it?
>
> It's sztarted as a daemon by a script. I have manually started it up
> with the same results.
>
> > I don't agree with the library theory, it looks to me that you are
> > running at l
> That sounds very plausible to me. :) Clever thinking. It might also
> account for his permission problems (as the cron environment for that user
> may differ). Trying "crontab -u clamav -l" might prove quite revealing. :)
>
I can say for certain that I did not put it into cron, and I have verif
> How do you start freshclam, as daemon or manually to test it?
It's sztarted as a daemon by a script. I have manually started it up with
the same results.
>
> I don't agree with the library theory, it looks to me that you are
> running at least two different copies of freshclam, one of them is t
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> René Berber
> Sent: woensdag 9 maart 2005 21:02
> To: clamav-users@lists.clamav.net
> Subject: [Clamav-users] Re: Two persistent problems with clamav
>
>
> How do you
Jerry Bell wrote:
[snip]
When I start up freshclam, I see this:
freshclam daemon 0.83 (OS: freebsd5.2.1, ARCH: i386, CPU: i386)
ClamAV update process started at Wed Mar 9 10:06:35 2005
main.cvd is up to date (version: 30, sigs: 31086, f-level: 4, builder: tkojm)
daily.cvd is up to date (version: 7
12 matches
Mail list logo