Date: Sat, 17 Jul 2010 10:15:55 +0200 From: Christof Schulze <christof.schulze@gmx.com> To: freebsd-current@freebsd.org Cc: Matthew Seaman <m.seaman@infracaninophile.co.uk>, Alex Kozlov <spam@rm-rf.kiev.ua>, Gabor Kovesdan <gabor@freebsd.org>, Lowell Gilbert <freebsd-current-local@be-well.ilk.org> Subject: Re: periodic script in base system to run csup Message-ID: <201007171016.14467.christof.schulze@gmx.com> In-Reply-To: <4C416307.9000001@infracaninophile.co.uk> References: <20100716143621.GA9281@ravenloft.kiev.ua> <44k4ov6nax.fsf@lowell-desk.lan> <4C416307.9000001@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4182512.5POp726C8H Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable > [periodic updating source] Besides technical feasibility: What is the use case behind it? Regards Christof Am Saturday 17 July 2010 10:00:07 schrieb Matthew Seaman: > On 17/07/2010 24:04:38, Lowell Gilbert wrote: > > Alex Kozlov <spam@rm-rf.kiev.ua> writes: > >> On Fri, Jul 16, 2010 at 04:27:39PM +0200, Gabor Kovesdan wrote: > >>> Em 2010.07.16. 16:23, Alex Kozlov escreveu: > >>>> On Fri, Jul 16, 2010 at 03:58:33PM +0200, Gabor Kovesdan=20 wrote: > >>>>=20 > >>>> Thousands pc simultaneously try to access cvsup servers? > >>>> Sound like a ddos to me. > >>>=20 > >>> Yes, this was the only concern and that's why I started this > >>> discussion. > >>=20 > >> And because its periodic, We can't use portsnap solution=20 (random delay > >> before csup start). > >=20 > > It's not completely impossible; periodic could spin off a=20 separate shell > > for it, with a random delay. It's not clear what the best way=20 to deal > > with the output would be, although several approaches present=20 themselves. > > It would be a lot more complicated than Gabor's approach,=20 though. >=20 > Simply ensuring the csup periodic job is the last one to run > (/etc/periodic/daily/1000.csup ?) should give you the best of both > worlds. You can insert a random delay of up to an hour and still=20 deal > with csup as a foreground job. All of the other periodic jobs=20 will run > as normal (and should help with randomising the time distribution=20 of the > csup runs too) -- you'll just have to wait a bit longer for the=20 nightly > e-mail to be produced. >=20 > Even so, I think this is still likely to upset the cvsup servers:=20 a > whole timezone worth of machines hitting a small number of servers > within one or two hours might be doable with portsnap / freebsd- update > but cvsup requires a lot more effort server-side. >=20 > Cheers >=20 > Matthew =2D-=20 () ascii ribbon campaign - against html e-mail=20 /\ www.asciiribbon.org - against proprietary attachments --nextPart4182512.5POp726C8H Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEABECAAYFAkxBZs4ACgkQpZfyPAmdZJkCpQCeMA6P33DNZtbMsTkdKaPO+o3f gdIAoLPhwjpy9cFABjSV9bJI3SkGVhBV =H9om -----END PGP SIGNATURE----- --nextPart4182512.5POp726C8H--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201007171016.14467.christof.schulze>