Hi there,
Some time ago somebody wrote, and somebody else replied:
Why not just run freshclam as a daemon?
Then you really need to have a daemon watcher to keep it going.
Talk of freshclam dying gives me some discomfort, yet in almost two
years running freshclam as a daemon on two - not
G.W. Haywood wrote:
Hi there,
Some time ago somebody wrote, and somebody else replied:
Why not just run freshclam as a daemon?
Then you really need to have a daemon watcher to keep it going.
Talk of freshclam dying gives me some discomfort, yet in almost two
years running freshclam as
On Fri, 29 Dec 2006 12:31:29 + (GMT)
G.W. Haywood [EMAIL PROTECTED] wrote:
Naturally if freshclam dies we can expect people to mention it. I'm
calling for those who run freshclam as a daemon and who don't see any
problems with it to chip into this thread. How many of us are there?
I run
On Fri, 2006-12-29 at 12:31 +, G.W. Haywood wrote:
Hi there,
Some time ago somebody wrote, and somebody else replied:
Why not just run freshclam as a daemon?
Then you really need to have a daemon watcher to keep it going.
Naturally if freshclam dies we can expect people to mention
Naturally if freshclam dies we can expect people to mention it. I'm
calling for those who run freshclam as a daemon and who don't see any
problems with it to chip into this thread. How many of us are there?
I run freshclam in daemon mode for several servers processing several
hundred
Two Linux boxes here, one Generic (used to be Caldera 2.2) and one
Fedora Core 5 been running it on both for close to 18 monthsnot
one failure that I'm aware of. Both boxes are fairly busy as well, the
caldera is an email/list/web box and the FC5 is a weather map
server/forecasting tools
G.W. Haywood wrote:
Hi there,
Some time ago somebody wrote, and somebody else replied:
Why not just run freshclam as a daemon?
Then you really need to have a daemon watcher to keep it going.
Talk of freshclam dying gives me some discomfort, yet in almost two
years running freshclam as a
Dennis Peterson wrote:
G.W. Haywood wrote:
Hi there,
Some time ago somebody wrote, and somebody else replied:
Why not just run freshclam as a daemon?
Then you really need to have a daemon watcher to keep it going.
Talk of freshclam dying gives me some discomfort, yet in almost two
years
On Fri, 2006-12-29 at 12:31 +, G.W. Haywood wrote:
Hi there,
Some time ago somebody wrote, and somebody else replied:
Why not just run freshclam as a daemon?
Then you really need to have a daemon watcher to keep it going.
Talk of freshclam dying gives me some discomfort, yet in
Jim Maul wrote:
Dennis Peterson wrote:
This is not rocket science.
Who said it was? The OP clearly asked for people who run freshclam as a
daemon who have NOT had problems with it in the setup. You are not one
of those people so im still trying to figure out why you felt the need
to
Dennis Peterson wrote:
Jim Maul wrote:
Dennis Peterson wrote:
This is not rocket science.
Who said it was? The OP clearly asked for people who run freshclam as
a daemon who have NOT had problems with it in the setup. You are not
one of those people so im still trying to figure out
I have a user that is sending themselves e-mails containing attachments of
web server logs on the last few days of each month that appear to be very
well compressed. When this happens, clamd seems to overheat.
88457 root 59 0 319M 207M RUN 8:28 90.82% 90.82% clamd
Notice the
Mark Hennessy wrote:
I have a user that is sending themselves e-mails containing attachments of
web server logs on the last few days of each month that appear to be very
well compressed. When this happens, clamd seems to overheat.
88457 root 59 0 319M 207M RUN 8:28 90.82%
G.W. Haywood wrote:
I'm calling for those who run freshclam as a daemon and who don't see
any problems with it to chip into this thread. How many of us are
there?
We're running freshclam as a daemon - probably for about 2 years, I'm
not sure. AFAIK, we have not seen any stability problems,
Dennis Peterson wrote:
[60 lines snipped]
I can only tell you from my experience with several years and many
versions of ClamAV that I have found no advantage in any category to
running freshclam as a daemon, and running it in cron gives me many
options not otherwise available - not the
Dennis Peterson wrote:
At some point you've got to trust someone/something. Who watches
your daemon watcher? Who watches your OS? Who watches your
power-supply?
I run SPARC equipment - I have monitoring for all that and cpu
temperature, too. There's a difference between proper monitoring
In message [EMAIL PROTECTED] Per Jessen [EMAIL PROTECTED]
wrote:
Dennis Peterson wrote:
At some point you've got to trust someone/something. Who watches
your daemon watcher? Who watches your OS? Who watches your
power-supply?
I run SPARC equipment - I have monitoring for all that and cpu
Dennis Peterson wrote:
[60 lines snipped]
I can only tell you from my experience with several years and many
versions of ClamAV that I have found no advantage in any category to
running freshclam as a daemon, and running it in cron gives me many
options not otherwise available -
Per Jessen wrote:
Dennis Peterson wrote:
And as an old school Unix admin who still believes in the mentoring
responsibility of my position, I will make recommendations from time
to time regarding best practices and I recommend if you run freshclam
as a daemon that you monitor it and restart
Dave Warren wrote:
We run Intel equipment (mostly) and monitor all that too. Still, it
sounds like you've decided to trust your daemon-watcher daemon? We do
not use daemon-watchers simply because it's impossible to tell when to
stop. If you trust your watcher, you might as well trust the
On Fri, Dec 29, 2006 at 09:16:03PM +0100, Per Jessen said:
Dennis Peterson wrote:
but I can guarantee freshclam can fail regularly (and has) when run as
a daemon.
Now that is WORRYING. Are the clamav developers listening in here? I
can't verify Dennis' statement myself, but if
On Fri, December 29, 2006 3:54 pm, Dennis Peterson said:
This thread has become fractious (I claim some responsibility) and
unhelpful to the project. Fortunately ClamAV supports all our methods and
we can apply our own disciplines to the problems we each see and that's a
good thing.
Just
Daniel T. Staal wrote:
Has anyone tried both? What happens if you try to run freshclam as a
daemon and from cron? (Assuming you schedule them to run at different
times, of course. If they both checked at the same time I would
expect something to bork.)
If they both ran at the same time,
Dave Warren wrote:
In message [EMAIL PROTECTED] Per Jessen [EMAIL PROTECTED]
wrote:
[ ... ]
There is no reason that monitors can't monitor other monitors too, in
the software world.
Sure. But there's a setup cost in terms of admin time, and at least some
resources being spent regardless of
On the subject of Cron,
When I was still running Fedora Core 3, I was running my freshclam's
using cron but found from time to time that when I came in to work in
the morning I would have 20 to 30 cron processes still holding on
chewing up resource but not finishing off anything.
This caused me
Barry Gill wrote:
On the subject of Cron,
When I was still running Fedora Core 3, I was running my freshclam's
using cron but found from time to time that when I came in to work in
the morning I would have 20 to 30 cron processes still holding on
chewing up resource but not finishing off
26 matches
Mail list logo
