Xref: utzoo comp.unix.questions:26780 comp.unix.internals:978
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!decuac!hussar.dco.dec.com!mjr
From: mjr@hussar.dco.dec.com (Marcus J. Ranum)
Newsgroups: comp.unix.questions,comp.unix.internals,alt.unix.wizards
Subject: Re: rcp behavior
Message-ID: <1990Nov8.152136.11355@decuac.dec.com>
Date: 8 Nov 90 15:21:36 GMT
References: <1990Nov5.192620.1467@nbc1.ge.com>
Sender: news@decuac.dec.com (Network News)
Organization: Digital Equipment Corp., Washington Ultrix Resource Center
Lines: 21

In article <1990Nov5.192620.1467@nbc1.ge.com> scott@nbc1.GE.COM (Scott Barman) writes:

>I wrote and maintaining a program that has to run on both Suns and
>MicroVaxes (not my choice so save your flames).  To make sure sources
>stay the same on all machines I am using my Makefile to rcp the changed
>sources to the other machines.

	I prefer to use rdist for such things - it's even smart enough
to not stomp on top of files that you want, check last update times, etc.
I really suggest you take a look at it. To head off yet another complaint
about DEC: rdist is not part of the older releases of ULTRIX (I assume
you must be running an old release if you're getting NFS errors) :-)
but its source is available for FTP on uunet.uu.net in bsd-sources.

	One other nice thing about rdist is it lets you specify whole
directories to remote-maintain, and lets you give "except-patters" so
you don't wind up copying your VAX binaries to the Suns.

	Was that a "flame" ?

mjr.