From owner-freebsd-questions@FreeBSD.ORG Mon Jun 2 09:49:18 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5597437B401 for ; Mon, 2 Jun 2003 09:49:18 -0700 (PDT) Received: from floyd.gnulife.org (floyd.gnulife.org [199.86.41.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76EA343FA3 for ; Mon, 2 Jun 2003 09:49:17 -0700 (PDT) (envelope-from jamie@gnulife.org) Received: by floyd.gnulife.org (Postfix, from userid 1000) id C401943308; Mon, 2 Jun 2003 11:53:08 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by floyd.gnulife.org (Postfix) with ESMTP id B5A95432FE for ; Mon, 2 Jun 2003 11:53:08 -0500 (CDT) Date: Mon, 2 Jun 2003 11:53:08 -0500 (CDT) From: Jamie To: freebsd-questions@freebsd.org Message-ID: <20030602113508.W33999-100000@floyd.gnulife.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Upgrading a live server with rdist X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2003 16:49:18 -0000 I am trying to upgrade a running production server with rdist, but some of the files will not update. I am getting messages like: rdist: server.foo.net:/bin/rcp: Operation not permitted updating: /kernel rdist: server.foo.net:/kernel: Operation not permitted updating: /sbin/init rdist: server.foo.net:/sbin/init: Operation not permitted It appears rdist will not allow updates on processes that are loaded and running in memory. Is there any way to accomplish this with rdist or one of it's cousins? We have one test machine which is identical to all our production servers new patches are compiled into and are then tested. If it tests okay, we'd like to be able to simply run rdist from there out to our other production systems. We've also considered sharing the /usr/src/ directory after the tests pass, and then recompiling the binaries on the remote systems, but to do that you need to run mergemaster on each machine and bring it into single user mode. We'd like to avoid that downtime, iff possible. Anyone have insight/suggestions that would help guide us? Thanks, - Jamie "A friend is someone who lets you have total freedom to be yourself."