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
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
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
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
12 matches
Mail list logo
