On Wednesday 23 February 2005 12:49 am, Rob MacGregor wrote:
> On Wed, 23 Feb 2005 00:49:20 +, Bob Hutchinson
>
> <[EMAIL PROTECTED]> wrote:
> > That is a good reason, and true too, I have found the freshclam daemon
> > not functioning on one occasion, so now I cron it. Another reason is to
> >
On Tuesday 22 February 2005 05:14 pm, René Berber wrote:
> Dale Walsh wrote:
> [snip]
>
> > I can't understand why everyone runs this through cron when it doesn't
> > eat much memory or cpu cycles when run as a daemon?
>
> If freshclam fails as a daemon you would not know it. If it fails as a
> cr
> The way I look at it, if you need something in cron to periodically check
> that the freshclam daemon hasn't died, you might as well just configure
> the updates exactly as you'd like them with cron itself.
If you "need" something to run constantly, why then check for it only
periodically, with
On Wednesday 23 Feb 2005 06:49, Rob MacGregor wrote:
> On Wed, 23 Feb 2005 00:49:20 +, Bob Hutchinson
>
> <[EMAIL PROTECTED]> wrote:
> > That is a good reason, and true too, I have found the freshclam daemon
> > not functioning on one occasion, so now I cron it. Another reason is to
> > spread
On Wed, 23 Feb 2005 00:49:20 +, Bob Hutchinson
<[EMAIL PROTECTED]> wrote:
>
> That is a good reason, and true too, I have found the freshclam daemon not
> functioning on one occasion, so now I cron it. Another reason is to spread
> the load by setting it to cron at odd times, it must help the
On Tuesday 22 Feb 2005 23:14, René Berber wrote:
> Dale Walsh wrote:
> [snip]
>
> > I can't understand why everyone runs this through cron when it doesn't
> > eat much memory or cpu cycles when run as a daemon?
>
> If freshclam fails as a daemon you would not know it. If it fails as a
> cron job,
On Tue, 22 Feb 2005, Cormack, Ken wrote:
> > I can't understand why everyone runs this through cron when it doesn't
> > eat much memory or cpu cycles when run as a daemon?
>
> I can think of lots of reasons.
The way I look at it, if you need something in cron to periodically check
that the freshcl
> I can't understand why everyone runs this through cron when it doesn't
> eat much memory or cpu cycles when run as a daemon?
Because with cron, one can vary the minutes-after-the-hour, to have finer
control over when it runs. Or to have it run more frequently on certain
days than on others...
On Feb 22, 2005, at 14:46, René Berber wrote:
[EMAIL PROTECTED] wrote:
Freshclam via cron
What sort of update intervals are people using, and can someone show
me a
working crontab entry? I've tried calling freshclam like this via a
crontab
entry
06 0 * * * /usr/local/bin/freshclam
BUt it doe
