Re: periodic script in base system to run csup
On 17/07/2010 24:04:38, Lowell Gilbert wrote: Alex Kozlov s...@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 wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Yes, this was the only concern and that's why I started this discussion. And because its periodic, We can't use portsnap solution (random delay before csup start). It's not completely impossible; periodic could spin off a separate shell for it, with a random delay. It's not clear what the best way to deal with the output would be, although several approaches present themselves. It would be a lot more complicated than Gabor's approach, though. 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 deal with csup as a foreground job. All of the other periodic jobs will run as normal (and should help with randomising the time distribution of the csup runs too) -- you'll just have to wait a bit longer for the nightly e-mail to be produced. Even so, I think this is still likely to upset the cvsup servers: 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. Cheers Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: periodic script in base system to run csup
[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 s...@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 wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Yes, this was the only concern and that's why I started this discussion. And because its periodic, We can't use portsnap solution (random delay before csup start). It's not completely impossible; periodic could spin off a separate shell for it, with a random delay. It's not clear what the best way to deal with the output would be, although several approaches present themselves. It would be a lot more complicated than Gabor's approach, though. 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 deal with csup as a foreground job. All of the other periodic jobs will run as normal (and should help with randomising the time distribution of the csup runs too) -- you'll just have to wait a bit longer for the nightly e-mail to be produced. Even so, I think this is still likely to upset the cvsup servers: 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. Cheers Matthew -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part.
Re: periodic script in base system to run csup
On Fri, Jul 16, 2010 at 07:04:38PM -0400, Lowell Gilbert wrote: Alex Kozlov s...@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 wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Yes, this was the only concern and that's why I started this discussion. And because its periodic, We can't use portsnap solution (random delay before csup start). It's not completely impossible; periodic could spin off a separate shell for it, with a random delay. It's not clear what the best way to deal with the output would be, although several approaches present themselves. It would be a lot more complicated than Gabor's approach, though. I think this is overengineering. I personally just put few lines in root's crontab: ? ? * * * * make -C /usr/src update' /dev/null and /etc/make.conf: SUPHOST=cvsup?.xx.FreeBSD.org SUP_UPDATE= true SUPFILE=/etc/site/supfile-rel #PORTSSUPFILE= /etc/site/supfile-port DOCSUPFILE= /etc/site/supfile-doc -- Adios ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: periodic script in base system to run csup
On Fri, 16 Jul 2010 09:58, Gabor Kovesdan wrote: In Message-Id: 4c406589.7030...@freebsd.org Hi folks, Steven Kreuzer wrote a periodic script to run csup updates with periodic daily. I've reviewed it and added support for multiple supfiles. I'd like to commit this to head. : http://kovesdan.org/files/600.csup : : Is there any objection? In a message listed in this thread someone has mentioned that this can already be done from cron. ( make -C /usr/src update ) at your own preferred time of updating. No offense but including something like this into the periodic system without a way to randomize the time at which it will actually run would be irresponsible while wreaking havoc on the source servers and I would strongly advise against it. *** If a way to randomize the time at which this is run is conceived and you wish to proceed I would also strongly advise that it is moved to a periodic weekly location instead. *** Personally I see updating your source tree as a interactive process unless for the use of a mirroring server which is not needed on every machine this would end up on. Adding this I only see results of blatant enabling the controls creating pointless mirrors. Maybe adding this to src/tools would be a better place or creating a port for this. With all do respect Regards, -- jhell,v ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
periodic script in base system to run csup
Hi folks, Steven Kreuzer wrote a periodic script to run csup updates with periodic daily. I've reviewed it and added support for multiple supfiles. I'd like to commit this to head. http://kovesdan.org/files/600.csup Is there any objection? Gabor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: periodic script in base system to run csup
On Fri, Jul 16, 2010 at 03:58:33PM +0200, Gabor Kovesdan wrote: Steven Kreuzer wrote a periodic script to run csup updates with periodic daily. I've reviewed it and added support for multiple supfiles. I'd like to commit this to head. http://kovesdan.org/files/600.csup Is there any objection? Hmm, /usr/src/Makefile has an 'update' target that can run csup and other updating tools. Perhaps it should call that instead? -- Jilles Tjoelker ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
periodic script in base system to run csup
On Fri, Jul 16, 2010 at 03:58:33PM +0200, Gabor Kovesdan wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Btw, if You have time, can You please check conf/124641? Thanks. -- Adios ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: periodic script in base system to run csup
Em 2010.07.16. 16:15, Jilles Tjoelker escreveu: Hmm, /usr/src/Makefile has an 'update' target that can run csup and other updating tools. Perhaps it should call that instead? It is not just for updating your src tree but your ports tree, doc tree or eventually your local CVS repo. That's why you can specify multiple supfiles. Gabor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: periodic script in base system to run csup
Em 2010.07.16. 16:23, Alex Kozlov escreveu: On Fri, Jul 16, 2010 at 03:58:33PM +0200, Gabor Kovesdan wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Yes, this was the only concern and that's why I started this discussion. Btw, if You have time, can You please check conf/124641? Thanks. Ok, looks interesting, will take a look. Gabor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: periodic script in base system to run csup
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 wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Yes, this was the only concern and that's why I started this discussion. And because its periodic, We can't use portsnap solution (random delay before csup start). -- Adios ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: periodic script in base system to run csup
Alex Kozlov s...@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 wrote: Thousands pc simultaneously try to access cvsup servers? Sound like a ddos to me. Yes, this was the only concern and that's why I started this discussion. And because its periodic, We can't use portsnap solution (random delay before csup start). It's not completely impossible; periodic could spin off a separate shell for it, with a random delay. It's not clear what the best way to deal with the output would be, although several approaches present themselves. It would be a lot more complicated than Gabor's approach, though. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
