From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DsMu0-0003Uc-Pj for garchives@archives.gentoo.org; Tue, 12 Jul 2005 15:42:33 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6CFdZDu018328; Tue, 12 Jul 2005 15:39:35 GMT Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6CFRl0x020896 for ; Tue, 12 Jul 2005 15:27:47 GMT Received: from mail.joat.com ([71.114.133.177]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IJI00BJ7TNP76HE@vms042.mailsrvcs.net> for gentoo-user@lists.gentoo.org; Tue, 12 Jul 2005 10:28:38 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.joat.com (Postfix) with ESMTP id 89E73510E; Tue, 12 Jul 2005 11:29:29 -0400 (EDT) Received: from mail.joat.com ([127.0.0.1]) by localhost (cornholio [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30843-04; Tue, 12 Jul 2005 11:29:25 -0400 (EDT) Received: from cdnebinge (jnet.state.pa.us [206.224.31.162]) by mail.joat.com (Postfix) with ESMTP; Tue, 12 Jul 2005 11:29:25 -0400 (EDT) Date: Tue, 12 Jul 2005 11:29:20 -0400 From: "Dave Nebinger" Subject: RE: [gentoo-user] Re: rsync internal mirror configuration In-reply-to: To: Cc: Message-id: <005e01c586f6$7997de80$5f01010a@jnetlab.lcl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Mailer: Microsoft Outlook, Build 10.0.6626 Content-type: text/plain; charset=us-ascii Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal DomainKey-Signature: a=rsa-sha1; h=Received:Received:From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:In-Reply-To:X-MimeOLE:Importance:X-Virus-Scanned; b=Yxzay8MroOIcSQb8fWh6Q+f+2ULZUgRqiUWDrCHSNtAachc1V3XIBhv6Us5GkFmZi3vSxYKOSATELFKJ14jcvNJmPdv6DHpPqTbkg2BBYMFx8nHkGnqTJcujOrEJw8HM/MwEQBaMQpLBzSGfJpwI2cCr0BFKnQ/wb8C6LtDh5pU=; c=nofws; d=joat.com; q=dns; s=selector1 X-Virus-Scanned: amavisd-new 2.3.1 (20050509) at joat.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j6CFRl0x020896 X-Archives-Salt: 283ffcbc-a503-4d4c-b2ac-9d28651b91e6 X-Archives-Hash: 6e4cbacdcbdec0b73b57a4e32894b451 > OK but can't I do that with a simple mode to the /etc/crontab ?: > 30 1 * * * root emerge sync 2>&1 > ? Yes, but I do a little more in my script and want the pieces to be synchronized. As you saw in the script not only do I emerge sync but I also update the eix and esearch databases (both are cached package search/query tools that kick the crap out of "emerge --search"). I've been considering adding an "emerge --fetchonly" line to the script but don't yet have the warm and fuzzies about the http-replicator script. > This script is for the internal rsync/replicator server? Runs on all of them. All of them need to sync and I like being able to query from whatever system I'm on. > OK, the port has changed. What's the deal about that? Most local http daemons run on 8080 or 8088; I just didn't want to deal with conflicts so I chose my own number. > OK thanks for the script. I'll have to study it, test it and let you know > how it goes... They've been working out great for me. I've recently added a 'revdep-rebuild' script so I can be reported of packages in need of fixing (in case I miss the step manually). > Agreed. But I intend to set up a test-quarrantine system that is fully > automated, and if all goes well for (1) 24-hour period, then push the > updates to a bunch of PI and PII systems for a bunch of kids (hoodlums.... > some of which are mine.) Ah, but how long would it take to test out the new package(s) in the quarantine system? When it's something significant (i.e. pam) are you going to test out every system component using pam before deploying internally? In your case I'd probably ensure the kids logins are typical user logins (no update capability). Run the scripts (or similar scripts) to automate the syncing and reporting. Keep ssh running on their systems. Hold off on updates until they run into something that breaks or until a critical package update is released. Then you can ssh in and emerge stuff until it works. Basically it's a question that even windows folks have to face - is it more important to have a working yet somewhat out of date system or a cutting-edge updated system that can sometimes be unstable? In my home I've chosen to keep my boxen up to date but the kids systems tend to lag well behind the curve. -- gentoo-user@gentoo.org mailing list