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 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 distributed about,
say, a day...
It's the same classic problem with uninspired admins, running such cron
jobs strictly at a full hour.
> > With the notable exception of the SOUGHT rule-set, there is no single
> > rule-set out there that's being updated even on a daily basis, let alone
> > hourly. Spam isn't "once a day", and spam evolves quite fast -- though
> > still not even close to daily...
> >
> > Even SOUGHT, which is being updated a few times a day, does *not*
> > require hourly updates. It isn't generated that often.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
