On Sun, 2009-03-29 at 13:55 -0700, RobertH wrote:
> Previously, Karsten Bräckelmann wrote:
> > The most part of this discussion isn't specific to you, nor
> > SA. It's a well-known, general problem when running update
> > services. It isn't meant to be a decree either, it's partly
> > my opinio
>
> Oh, come on, Robert -- I didn't say your way is abusive, just
> overkill.
>
> The most part of this discussion isn't specific to you, nor
> SA. It's a well-known, general problem when running update
> services. It isn't meant to be a decree either, it's partly
> my opinion, partly best-p
On Sun, 2009-03-29 at 13:05 -0700, RobertH wrote:
> > From: Karsten Bräckelmann
> > The real impact isn't the DNS query, but whenever an update
> > has been pushed. If everyone would check once an hour, the
> > full load would have to be shouldered in 60 minutes, as
> > opposed to evenly distri
Karsten Bräckelmann a écrit :
> On Sun, 2009-03-29 at 20:44 +0200, mouss wrote:
>> Karsten Bräckelmann a écrit :
>
>>> It's the same classic problem with uninspired admins, running such cron
>>> jobs strictly at a full hour.
>> In most cases, it's not the admins fault. many systems allow adding cr
> Mouss wrote:
> In most cases, it's not the admins fault. many systems allow
> adding cron jobs by simply putting a file in a
> /some/path/hourly and so on instead of editing /etc/crontab
> (or running the crontab command). This is nice (exceptionally
> for packages when editing files is p
> From: Karsten Bräckelmann
> Heh, true. And he could run sa-update even more frequently.
> After all, the DNS answer is cached for an hour... ;)
>
> The real impact isn't the DNS query, but whenever an update
> has been pushed. If everyone would check once an hour, the
> full load would hav
On Sun, 2009-03-29 at 20:44 +0200, mouss wrote:
> Karsten Bräckelmann a écrit :
> > It's the same classic problem with uninspired admins, running such cron
> > jobs strictly at a full hour.
>
> In most cases, it's not the admins fault. many systems allow adding cron
> jobs by simply putting a fil
Karsten Bräckelmann a écrit :
> On Sun, 2009-03-29 at 18:14 +0100, Justin Mason wrote:
>> on the other hand, the sa-update architecture can cope with it just fine. ;)
>
> Heh, true. And he could run sa-update even more frequently. After all,
> the DNS answer is cached for an hour... ;)
>
> The re
On Sun, 2009-03-29 at 18:14 +0100, Justin Mason wrote:
> on the other hand, the sa-update architecture can cope with it just fine. ;)
Heh, true. And he could run sa-update even more frequently. After all,
the DNS answer is cached for an hour... ;)
The real impact isn't the DNS query, but whenever
on the other hand, the sa-update architecture can cope with it just fine. ;)
2009/3/29 Karsten Bräckelmann :
>> > Isn't that a tad overkill?
>
> It is. :)
>
>> > http://wiki.apache.org/spamassassin/RuleUpdates
>> >
>> > How often should I run sa-update?
>> >
>> > As often as you like. It typically
10 matches
Mail list logo
