From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 15:03:57 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B676F1065677 for ; Sun, 23 Oct 2011 15:03:57 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 63BE38FC20 for ; Sun, 23 Oct 2011 15:03:57 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1RHzag-0009RL-H5 for freebsd-stable@freebsd.org; Sun, 23 Oct 2011 17:03:58 +0200 Date: Sun, 23 Oct 2011 17:03:58 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Message-ID: <20111023150358.GS28186@home.opsec.eu> References: <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> <9E8E59C0-5FE6-4193-9A01-8A2DFBC311F7@lassitu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: Running portupgrade from cron (was: /usr/bin/script eating 100% cpu with portupgrade and xargs) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 15:03:57 -0000 Hi! > >>>> Worst of all, you're running portupgrade from cron without > >>>> reading UPDATING, which is just asking for trouble. > >>> What specifically is your concern here? > Yes, but updating correctly in first place is better than trying to > understand what happened to software looking for libpng.so.N when > there is libpng.so.N+1 and _then_ reading UPDATING is better, don't > you think? It depends. I have reference boxes which daily run portupgrade from cron, just to see whether I have a consistent set of ports for our apps. If most of the packages are stable, I'll generate a pkg collection and replicate it to those destination hosts that need updating and replace every pkg on those hosts with new pkgs. > Other point is that during update daemons never restarted. But > sometimes stopped, dovecot, for example, if I'm not mistaken. Do you > also reboot after each cron update? As the reference boxes do not run services, that's not a problem. To sum it up: running portupgrade from cron is useful. -- pi@opsec.eu +49 171 3101372 9 years to go !