Thanks,
It helps :)
Christopher X. Candreva wrote:
On Thu, 14 Sep 2006, Aleksey Luzin wrote:
# freshclam
ERROR: Problem with internal logger.
What does it mean? and how I can fix it?
It means there is another instance of freshclam running. If it's still
running, kill it.
___
On Thu, 14 Sep 2006, Aleksey Luzin wrote:
>
> # freshclam
> ERROR: Problem with internal logger.
>
> What does it mean? and how I can fix it?
It means there is another instance of freshclam running. If it's still
running, kill it.
==
Chr
Kris Deugau wrote:
Chuck Swiger wrote:
Only, when they use a mechanism like ports/pkgsrc/dselect/yum/etc to
update the installed version of freshclam, that mechanism leaves the
old version of the daemon running rather than stopping and restarting
freshclam to pick up the new version.
Or wors
Chuck Swiger wrote:
Only, when they use a mechanism like ports/pkgsrc/dselect/yum/etc to
update the installed version of freshclam, that mechanism leaves the old
version of the daemon running rather than stopping and restarting
freshclam to pick up the new version.
Or worse, inists on (re)ins
Chuck Swiger wrote:
Only, when they use a mechanism like ports/pkgsrc/dselect/yum/etc to
update the installed version of freshclam, that mechanism leaves the old
version of the daemon running rather than stopping and restarting
freshclam to pick up the new version.
This problem depends upon
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
What is the best solution to ensure reliable updates without manual
intervention? Just ensure that the cron job kills any old instances
of freshclam before running a new one?
Why not just run it as a daemon?
Apparently, that's just what the
[EMAIL PROTECTED] wrote:
What is the best solution to ensure reliable updates without manual
intervention? Just ensure that the cron job kills any old instances of
freshclam before running a new one?
Why not just run it as a daemon?
Steve
___
h
On Tue, Aug 29, 2006 at 06:33:05PM +0200, [EMAIL PROTECTED] wrote:
>
> The above log report is an indication of a failed freshclam update. It is
> annoying, because it generally means that no updates will work from then
> on - it doesn't fix itself. It seems to be caused by an old instance of
>
