From owner-freebsd-isp Mon Jul 12 15:52: 5 1999 Delivered-To: freebsd-isp@freebsd.org Received: from rip.ops.neosoft.com (rip.ops.NeoSoft.COM [206.109.4.20]) by hub.freebsd.org (Postfix) with ESMTP id 8A32715034 for ; Mon, 12 Jul 1999 15:52:03 -0700 (PDT) (envelope-from awsmith@rip.ops.neosoft.com) Received: (from awsmith@localhost) by rip.ops.neosoft.com (8.9.2/8.9.1) id RAA43486; Mon, 12 Jul 1999 17:49:33 -0500 (CDT) (envelope-from awsmith) Message-ID: <19990712174933.C43258@ops.neosoft.com> Date: Mon, 12 Jul 1999 17:49:33 -0500 From: "Andrew W. Smith" To: "f.johan.beisser" , Alejandro Ramirez Cc: freebsd-isp@FreeBSD.ORG Subject: Re: updating multiple machines.. References: <001b01beccb3$53946900$fca3f9cf@megared.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from f.johan.beisser on Mon, Jul 12, 1999 at 03:39:36PM -0700 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Jul-1999, f.johan.beisser wrote: > > kinda breaks the secured machines. these servers are locked down and > protected because they are in effect gateway machines. > > one solution i heard of (but haven't been able to get to work) is to copy > (rdist? rsync?) the /opt directory from the build machine to the intended > update machines. > > any thoughts on this? > > jan rdist using ssh-agent and -P ssh instead of rsh should work great as long as you are basically replicating binaries to remote machines for your -stable upgrades. --------------------------------------------------------------------------- ** Andrew W. Smith ** awsmith@neosoft.com ** Chief Network Engineer ** ** http://www.neosoft.com/neosoft/staff/andrew ** 1-888-NEOSOFT ** ** "Opportunities multiply as they are seized" - Sun Tzu ** --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message