Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 2 Mar 2005 16:37:39 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	"DePriest, Jason R." <jrdepriest AT gmail DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Keeping cygwin updated on remote systems
In-Reply-To:	<31b7d279050302120875fa9734@mail.gmail.com>
Message-ID:	<Pine.GSO.4.61.0503021631130.2585@slinky.cs.nyu.edu>
References:	<31b7d279050302120875fa9734 AT mail DOT gmail DOT com>
MIME-Version:	1.0

On Wed, 2 Mar 2005, DePriest, Jason R. wrote:

> I have about 20 systems that are either behind firewalls that I don't
> control or hardened so that my only access to them is via SSH.
>
> I am using OpenSSH installed with the Cygwin setup.exe program and
> configured with the included scripts.
>
> I also tunnel VNC through SSH to get a remote desktop when necessary.
>
> My problem is: how do I keep these systems updated since my only
> access is through the components I need to update?
>
> I am also trying to find a way to avoid manually connecting to each
> system to run setup.exe and then rebooting it so in-use files can be
> updated.
>
> Does anyone have any methods they use to handle this?

I take it a network drive for /bin, /lib, and /usr is not an option?

> The 20 systems should all be mostly identical.  So my first thought
> was to create a representative build in a test lab, keep it updated,
> and then batch an rsync over SSH of the files to the 20 systems
> identically up-to-date.
>
> How can I handle in-use files if I am not using setup.exe?
>
> I would love to hear any suggestions that anyone has.

The same way setup.exe handles them -- if replacement fails, schedule one
on reboot.  Someone posted a perl script for getting those out of the
on-reboot replacement list; I'm sure you can use similar techniques for
getting them on that list.

But I would go with the shared network drive approach, if at all possible.
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -