From owner-freebsd-questions@FreeBSD.ORG Mon Nov 26 15:36:39 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FFC0A14 for ; Mon, 26 Nov 2012 15:36:39 +0000 (UTC) (envelope-from lists@legolasweb.nl) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) by mx1.freebsd.org (Postfix) with ESMTP id 4FEE68FC14 for ; Mon, 26 Nov 2012 15:36:38 +0000 (UTC) Received: from [212.54.42.133] (helo=smtp2.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1Td0je-0002Li-5C for freebsd-questions@freebsd.org; Mon, 26 Nov 2012 16:36:38 +0100 Received: from 5357e32a.cm-6-8d.dynamic.ziggo.nl ([83.87.227.42] helo=homey.local) by smtp2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1Td0jd-0001vX-PD for freebsd-questions@freebsd.org; Mon, 26 Nov 2012 16:36:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 26 Nov 2012 16:37:50 +0100 From: Stas Verberkt To: Subject: Re: When Is The Ports Tree Going To Be =?UTF-8?Q?Updated=3F?= In-Reply-To: References: <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org> <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com> <50B2BEE1.9030903@tundraware.com> <50B31AAB.6000903@FreeBSD.org> <50B36500.7040308@tundraware.com> <50B377F4.1020507@freebsd.org> <20121126145818.GA66335@neutralgood.org> Message-ID: X-Sender: lists@legolasweb.nl User-Agent: Roundcube Webmail/0.8.4 X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.7 X-Ziggo-spamreport: ALL_TRUSTED=-1, BAYES_00=-1.9, PROLO_TRUST_RDNS=-3, RDNS_DYNAMIC=0.982, SPF_SOFTFAIL=0.2 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 15:36:39 -0000 Warren Block schreef op : > On Mon, 26 Nov 2012, kpneal@pobox.com wrote: > >> On Mon, Nov 26, 2012 at 02:08:52PM +0000, Matthew Seaman wrote: >>> Secondly, for the sake of the servers, please don't run 'portsnap >>> fetch' >>> from a cron job. You're not the only person to think of doing >>> that, and >>> most people who do have the job run at the top of the hour. This >>> is >>> bad. The servers really don't like it when several thousand >>> cronjobs >>> all fire off simultaneously and the system load goes through the >>> roof. >>> Which is why 'portsnap cron' exists -- it does exactly the same as >>> fetch, except it waits for a random amount of time before pulling >>> down >>> any data. >> >> More generally, a cron job can be run with a random delay added >> before >> the real job kicks off. Just prefix the command you want cron to run >> like so: >> >> sleep $(jot -r 1 1 900) && command to run >> >> If you like, replace 900 with some other number to change the upper >> bound >> on the number of seconds to delay. > > portsnap has a "cron" command that does this. > If I recall correctly portsnap refuses to run the "fetch"-command when not in an interactive shell, thereby forcing you to use the "cron"-command. (As does freebsd-update.)