How to prevent batch rsync to write rsync_argvs files in the home directory
Surabhi Choudhury
surabhi_choudhury at infosys.com
Sat Oct 26 04:51:01 EST 2002
Hi,
Whenever i am using the command
rsync --write-batch -av --stats `cat $1` -e ssh user at remote machine:/destination/
This is writing rsync_argvs files in the home directory as well as to the destination directory.
Can anyone give me any idea as how to prevent the writing of rsync_argvs files in the home directory which is of no use.
Regards,
Surabhi.
> ----------
> From: rsync-request at lists.samba.org
> Reply To: rsync at lists.samba.org
> Sent: Friday, October 25, 2002 4:54 PM
> To: rsync at lists.samba.org
> Subject: rsync digest, Vol 1 #945 - 9 msgs
>
> Send rsync mailing list submissions to
> rsync at lists.samba.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.samba.org/mailman/listinfo/rsync
> or, via email, send a message with subject or body 'help' to
> rsync-request at lists.samba.org
>
> You can reach the person managing the list at
> rsync-admin at lists.samba.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of rsync digest..."
>
>
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
>
> ---------------------------------------
>
> Today's Topics:
>
> 1. Re: Mutliple backups into a signle dir (=?iso-8859-2?Q?Milan_Kr=E8m=E1=F8?=)
> 2. Re: Mutliple backups into a signle dir (jw schultz)
> 3. Re: rsync ownership problem via ssh? (jw schultz)
> 4. Re: rsync -e ssh does not work well (jw schultz)
> 5. Win32 Version? (wolfe-mcse at ev1.net)
> 6. Re: Win32 Version? (bart.coninckx at sita.be)
> 7. Re: rsync -e ssh does not work well (Kauko Heikkila)
> 8. Win32 Version? (David Starks-Browning)
> 9. Re: rsync -e ssh does not work well (jw schultz)
>
> --__--__--
>
> Message: 1
> Date: Fri, 25 Oct 2002 00:22:05 +0200
> From: =?iso-8859-2?Q?Milan_Kr=E8m=E1=F8?= <milan.krcmar at seznam.cz>
> To: rsync at lists.samba.org
> Subject: Re: Mutliple backups into a signle dir
>
> On Thu, Oct 17, 2002 at 06:03:56PM -0700, jw schultz wrote:
> > You might look at dirvish http://www.pegasys.ws/dirvish It
> > manages a complete rotation schedule with images preserved
> > for various periods.
> >
> > Someone else has another tool that is simpler but less
> > featureful that manages a fixed size image cycle.
> >
> > With both you get something akin to snapshots so that
> > restores are very easy.
>
> Thank you. Originally I had another idea, I didn't suppose to have
> complete backups but rather multiple versions of modificated files
> in a single place. Both method have their pros and cons, but with the
> dirvish you've persuaded me to unconditionally choose complete snapshots.
> It took me some time to try, test and setup the dirvish. I find it very
> usefull and would recommend it to everyone seeking a backup solution
> on harddisk media (although the possibility to backup on a tape and
> totaly take it out of reach of the computer remains a good argument for me
> to use tapes).
>
> I will send some tiny proposals for enhancement of dirvish to your
> personal e-mail if there isn't any list devoted to dirvish.
>
> Milan Krcmar
>
> --__--__--
>
> Message: 2
> Date: Thu, 24 Oct 2002 15:30:01 -0700
> From: jw schultz <jw at pegasys.ws>
> To: rsync at lists.samba.org
> Subject: Re: Mutliple backups into a signle dir
>
> On Fri, Oct 25, 2002 at 12:22:05AM +0200, Milan Kr?m?? wrote:
> > On Thu, Oct 17, 2002 at 06:03:56PM -0700, jw schultz wrote:
> > > You might look at dirvish http://www.pegasys.ws/dirvish It
> > > manages a complete rotation schedule with images preserved
> > > for various periods.
> > >
> > > Someone else has another tool that is simpler but less
> > > featureful that manages a fixed size image cycle.
> > >
> > > With both you get something akin to snapshots so that
> > > restores are very easy.
> >
> > Thank you. Originally I had another idea, I didn't suppose to have>
> > complete backups but rather multiple versions of modificated files
> > in a single place. Both method have their pros and cons, but with the
> > dirvish you've persuaded me to unconditionally choose complete snapshots.
>
> > It took me some time to try, test and setup the dirvish. I find it very
>
> The project is still young and documentation is not my best
> suit. Do let me know how, or if this could be helped.
>
> > usefull and would recommend it to everyone seeking a backup solution
> > on harddisk media (although the possibility to backup on a tape and
> > totaly take it out of reach of the computer remains a good argument for me
> > to use tapes).
>
> The FAQ makes it clear i consider off site storage important
> and removable media is still the best for archives.
>
> > I will send some tiny proposals for enhancement of dirvish to your
> > personal e-mail if there isn't any list devoted to dirvish.
>
> No list yet. If you prefer you can send to
> dirvish at pegasys.ws and it will get to me.
>
> If you drop me a line i'll know to notify you (bcc) when
> there are updates.
>
> Any more should go off-list.
>
> --
> ________________________________________________________________
> J.W. Schultz Pegasystems Technologies
> email address: jw at pegasys.ws
>
> Remember Cernan and Schmitt
>
> --__--__--
>
> Message: 3
> Date: Thu, 24 Oct 2002 15:48:05 -0700
> From: jw schultz <jw at pegasys.ws>
> To: rsync at lists.samba.org
> Subject: Re: rsync ownership problem via ssh?
>
> On Thu, Oct 24, 2002 at 12:29:31PM -0400, dmaloy at provide.net wrote:
> > I am using rsync to sync filesystems from one Solaris
> > machine to another at a remote site. Everything sync's
> > fine, except for the ownership preservation. The
> > permissions all get transferred correctly and so do all the
> > files, but the ownership always gets changed to whomever I
> > perform the sync as. I tried this as root and still the
> > same problem. I am using the -p, -o and -g options to
> > preserve the permissions, owner and group respectively. The
> > man page seems to imply that as "root" this works? I have
> > not found this to be the case. I am using ssh when
> > transmitting the data.
> >
> > Can someone please help?
>
> What you are describing doesn't jibe so i'll ask
> a couple of "is it plugged in" questions.
>
> Is it root on the receiver? For this the sender uid doesn't
> matter.
>
> Are the same user names on both ends (case and spelling
> matter).
>
> Did you try --numeric-ids? Not really appropriate if the
> same users have different IDs but maybe worth a try.
>
> Have you run with -v or -vvv and what about the rsync log.
>
> --
> ________________________________________________________________
> J.W. Schultz Pegasystems Technologies
> email address: jw at pegasys.ws
>
> Remember Cernan and Schmitt
>
> --__--__--
>
> Message: 4
> Date: Thu, 24 Oct 2002 15:55:11 -0700
> From: jw schultz <jw at pegasys.ws>
> To: rsync at lists.samba.org
> Subject: Re: rsync -e ssh does not work well
>
> On Thu, Oct 24, 2002 at 09:44:38PM +0300, Kauko Heikkila wrote:
> > 1.From SuSe Linux Enterpise server to another one:
> > rsync -trvuz -e ssh file.wrk uname at servername:uname-html
> > works wierdly since file.wrk changes
> > to a file named uname-html in the user's "uname" home.
>
> It did as you told it. try
> rsync -trvuz -e ssh file.wrk uname at servername:uname-html/
> if you want to put file.wrk inside the directory uname-html
> otherwise if you provide one file for the source and what
> appears to be a file as the destination...
>
>
>
> --
> ________________________________________________________________
> J.W. Schultz Pegasystems Technologies
> email address: jw at pegasys.ws
>
> Remember Cernan and Schmitt
>
> --__--__--
>
> Message: 5
> From: <wolfe-mcse at ev1.net>
> To: <rsync at lists.samba.org>
> Subject: Win32 Version?
> Date: Fri, 25 Oct 2002 00:27:36 -0500>
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0043_01C27BBD.52578CE0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> Howdy...
>
>
> I have searched the archives, and even read what has been posted on the site
> regarding a Win32 port of rsync. Though I have found a problem with
> everything. The URLs for building your own, or downloading the compiled
> binaries for the Win32 platform are no longer valid. Therein the problem
> lies, as the information is outdated, and still easily available on the site
> publicly.
>
> I imagine there are a few, and I mean a spare few, that are still using
> Windows 95, but most have moved onto either Windows 98, Windows ME, Windows
> NT 4.0, Windows 2000, Windows XP, or Windows .NET, but not necessarily to
> Unix, Linux, Solaris, AIX, or other non-Microsoft platform.
>
> I have downloaded the source code, and though I have not had a chance in
> which to look over it thoroughly, I hope to eventually develop enough
> familiarity so that I can port it over to the Win32, Win64, and .NET
> platforms.
>
> I know some of you may think that I am off my rocker when I mention the
> Win64 platform, but what you don't know is that Microsoft now has a 64-bit
> version of Windows XP, which can address 16 terabytes
> (18,446,744,073,709,551,616 bytes) of memory. I am just not sure if they
> have released it yet for purchase, but I do have authorized access to it,
> along with its support/diagnostic utilities.
>
> Now here is my question/suggestion...
>
> What is the current interest in a port of rsync to the Microsoft Windows
> platform?
>
> Is anyone interested in helping port rsync to the Microsoft Windows
> platform?
>
> I have a currently active Universal MSDN subscription, which includes Visual
> Studio 6.0 Enterprise, and Visual Studio .NET Enterprise Architect, and
> would be willing to provide any resources I have to this project if there is
> enough interest. In addition to this, I also have the Catalyst SocketTools
> Enterprise Edition library, should it be needed.
>
> For those who are interested, I would prefer an off-list reply, otherwise I
> may miss the message as it passes through my e-mail filters, and is placed
> in a different folder.
>
>
> Richard
>
> ------=_NextPart_000_0043_01C27BBD.52578CE0
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
>
>
> <META content=3D"MSHTML 5.50.4919.2200" name=3DGENERATOR></HEAD>
> <BODY>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2>Howdy...</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>I =
> have searched=20
> the archives, and even read what has been posted on the site regarding a =
> Win32=20
> port of rsync. Though I have found a problem with =
> everything. The=20
> URLs for building your own, or downloading the compiled binaries for the =
> Win32=20
> platform are no longer valid. Therein the problem lies, as the =
> information=20
> is outdated, and still easily available on the site=20
> publicly.</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>I =
> imagine there=20
> are a few, and I mean a spare few, that are still using Windows 95, but =
> most=20
> have moved onto either Windows 98, Windows ME, Windows NT 4.0, Windows =
> 2000,=20
> Windows XP, or Windows .NET, but not necessarily to Unix, Linux, =>
> Solaris, AIX,=20
> or other non-Microsoft platform.</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>I =
> have downloaded=20
> the source code, and though I have not had a chance in which to look =
> over it=20
> thoroughly, I hope to eventually develop enough familiarity so that I =
> can port=20
> it over to the Win32, Win64, and =
> .NET platforms.</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>I =
> know some of you=20
> may think that I am off my rocker when I mention the Win64 platform, but =
> what=20
> you don't know is that Microsoft now has a 64-bit version of Windows XP, =
> which=20
> can address 16 terabytes (18,446,744,073,709,551,616 bytes) of =
> memory. I=20
> am just not sure if they have released it yet for purchase, but I do =
> have=20
> authorized access to it, along with its support/diagnostic=20
> utilities.</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>Now =
> here is my=20
> question/suggestion...</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>What =
> is the=20
> current interest in a port of rsync to the Microsoft Windows=20
> platform?</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>Is =
> anyone=20
> interested in helping port rsync to the Microsoft Windows=20
> platform?</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>I =
> have a currently=20
> active Universal MSDN subscription, which includes Visual Studio 6.0 =
> Enterprise,=20
> and Visual Studio .NET Enterprise Architect, and would be willing to =
> provide any=20
> resources I have to this project if there is enough interest. In =
> addition=20
> to this, I also have the Catalyst SocketTools Enterprise Edition =
> library, should=20
> it be needed.</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana size=3D2>For =
> those who are=20
> interested, I would prefer an off-list reply, otherwise I may miss the =
> message=20
> as it passes through my e-mail filters, and is placed in a different=20
> folder.</FONT></SPAN></DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D000122004-25102002><FONT face=3DVerdana=20
> size=3D2>Richard</FONT></SPAN></DIV></BODY></HTML>
>
> ------=_NextPart_000_0043_01C27BBD.52578CE0--
>
>
> --__--__--
>
> Message: 6
> Subject: Re: Win32 Version?
> To: <wolfe-mcse at ev1.net>
> Cc: rsync at lists.samba.org, rsync-admin at lists.samba.org
> From: bart.coninckx at sita.be
> Date: Fri, 25 Oct 2002 09:20:42 +0200
>
>
> We use Rsync on NT very intensively. In fact, right now I backup about 25
> servers across WAN-links with the lates version of Rsync. You can compile
> it yourself to a Win32 binary by using the incredible Cygwin utilities
> (www.cygwin.com).
>
>
> Rgds,
>
>
> Bart Coninckx
> Network Administrator
> CNE, ASE
> *************************************
> Watco ICT Services
> Lilsedijk 19>
> B-2340 Beerse
> Belgium
>
> e-mail: bart.coninckx at sita.be
> Tel: + 32 (0) 14 60 99 42
> Fax: + 32 (0) 14 62 41 47
> *************************************
>
>
>
>
>
>
> <wolfe-mcse at ev1.n
> et> To: <rsync at lists.samba.org>
> Sent by: cc:
> rsync-admin at lists Subject: Win32 Version?
> .samba.org
>
>
> 10/25/2002 07:27
>
>
>
>
>
> Howdy...
>
>
> I have searched the archives, and even read what has been posted on the
> site regarding a Win32 port of rsync. Though I have found a problem with
> everything. The URLs for building your own, or downloading the compiled
> binaries for the Win32 platform are no longer valid. Therein the problem
> lies, as the information is outdated, and still easily available on the
> site publicly.
>
> I imagine there are a few, and I mean a spare few, that are still using
> Windows 95, but most have moved onto either Windows 98, Windows ME, Windows
> NT 4.0, Windows 2000, Windows XP, or Windows .NET, but not necessarily to
> Unix, Linux, Solaris, AIX, or other non-Microsoft platform.
>
> I have downloaded the source code, and though I have not had a chance in
> which to look over it thoroughly, I hope to eventually develop enough
> familiarity so that I can port it over to the Win32, Win64, and .NET
> platforms.
>
> I know some of you may think that I am off my rocker when I mention the
> Win64 platform, but what you don't know is that Microsoft now has a 64-bit
> version of Windows XP, which can address 16 terabytes
> (18,446,744,073,709,551,616 bytes) of memory. I am just not sure if they
> have released it yet for purchase, but I do have authorized access to it,
> along with its support/diagnostic utilities.
>
> Now here is my question/suggestion...
>
> What is the current interest in a port of rsync to the Microsoft Windows
> platform?
>
> Is anyone interested in helping port rsync to the Microsoft Windows
> platform?
>
> I have a currently active Universal MSDN subscription, which includes
> Visual Studio 6.0 Enterprise, and Visual Studio .NET Enterprise Architect,
> and would be willing to provide any resources I have to this project if
> there is enough interest. In addition to this, I also have the Catalyst
> SocketTools Enterprise Edition library, should it be needed.
>
> For those who are interested, I would prefer an off-list reply, otherwise I
> may miss the message as it passes through my e-mail filters, and is placed
> in a different folder.
>
>
> Richard
>
>
>
>
> --__--__--
>
> Message: 7
> From: "Kauko Heikkila" <Kauko.Heikkila at helsinki.fi>
> To: <rsync at lists.samba.org>
> Subject: Re: rsync -e ssh does not work well>
> Date: Fri, 25 Oct 2002 12:38:03 +0300
>
> Thanks for the answer. I fully appreciate.
>
> And in a way I admit what you said,
> but if you think of the command
>
> rsync -trvuz file.wrk uname at servername::uname-html
>
> what it does, then according to my logic
>
> rsync -trvuz -e ssh file.wrk uname at servername:uname-html
>
> should do exactly the same thing. Another thing would be
> to say, that it originally is not realizable in this
> way....
> and why not?
>
> Otherwise there is reconsideration of my perl
> procedures not made by me. And same with the directories
> that should only be known at the server side, not the
> client
> side, according to my logic. Perhaps I am wrong again,
> but currently cannot understand why I should tell all the
> clients if I want to change something in
> the server. Using rsync again for this purpose, perhaps.
> -All right, adding symbolic links to Linux and slashes
> to the procedures.
> But it is not that beautiful any more....-
> I might do that, but currently I am not contented with the
> nonsymmetric behaviour of rsync....I will start studying
> port forwarding soon......and use rsync in that way if it
> helps....
>
> sincerely
> Kauko
>
> ----- Original Message -----
> From: "jw schultz" <jw at pegasys.ws>
> To: <rsync at lists.samba.org>
> Sent: Friday, October 25, 2002 1:55 AM
> Subject: Re: rsync -e ssh does not work well
>
>
> > On Thu, Oct 24, 2002 at 09:44:38PM +0300, Kauko Heikkila
> wrote:
> > > 1.From SuSe Linux Enterpise server to another one:
> > > rsync -trvuz -e ssh file.wrk
> uname at servername:uname-html
> > > works wierdly since file.wrk changes
> > > to a file named uname-html in the user's "uname" home.
> >
> > It did as you told it. try
> > rsync -trvuz -e ssh file.wrk
> uname at servername:uname-html/
> > if you want to put file.wrk inside the directory
> uname-html
> > otherwise if you provide one file for the source and what
> > appears to be a file as the destination...
> >
> >
> >
> > --
> >
> ___________________________________________________________
> _____
> > J.W. Schultz Pegasystems Technologies
> > email address: jw at pegasys.ws
> >
> > Remember Cernan and Schmitt
> > --
> > To unsubscribe or change options:
> http://lists.samba.org/mailman/listinfo/rsync
> > Before posting, read:
> http://www.tuxedo.org/~esr/faqs/smart-questions.html
> >
>
>
> --__--__--
>
> Message: 8
> Date: Fri, 25 Oct 2002 10:50:48 +0100
> From: David Starks-Browning <starksb at ebi.ac.uk>
> To: <wolfe-mcse at ev1.net>
> Cc: <rsync at lists.samba.org>
> Subject: Win32 Version?
>
> On Friday 25 Oct 02, wolfe-mcse at ev1.net writes:
> > Howdy...
> >
> >
> > I have searched the archives, and even read what has been posted on the site
> > regarding a Win32 port of rsync. Though I have found a problem with
> > everything. The URLs for building your own, or downloading the compiled
> > binaries for the Win32 platform are no longer valid. Therein the problem
> > lies, as the information is outdated, and still easily available on the site
> > publicly.
>
> If you give precise details, maybe the rsync.samba.org maintainer(s)
> can repair the information.
>
> > What is the current interest in a port of rsync to the Microsoft Windows
> > platform?
> >
> > Is anyone interested in helping port rsync to the Microsoft Windows
> > platform?
>
> There is already a "Cygwin" port of rsync. In fact you can download
> rsync along with Cygwin from <http://cygwin.com/>. There is at least
> one "minimalist" distribution that includes only rsync, ssh and
> cygwin1.dll (and sources, of course) so you can skip all the
> other brilliant stuff that comes with a "default" Cygwin setup.
>
> However, there are problems with the Cygwin "port". Cygwin does not
> support large files (> 2GB). Cygwin will not attempt to support new
> versions of Microsoft Windows until they are officially released.
> Moreover, when the new Windows *is* released, updating Cygwin will>
> depend on the contributions of volunteers. (Like yourself, perhaps?)
>
> I believe that a true "native" Windows port (i.e., one that does not
> require the UNIX emulation layer that Cygwin provides) would be quite
> difficult.
>
> Hope this answers some of your questions.
>
> Regards,
> David
>
>
> --__--__--
>
> Message: 9
> Date: Fri, 25 Oct 2002 04:23:45 -0700
> From: jw schultz <jw at pegasys.ws>
> To: rsync at lists.samba.org
> Subject: Re: rsync -e ssh does not work well
>
> On Fri, Oct 25, 2002 at 12:38:03PM +0300, Kauko Heikkila wrote:
> > Thanks for the answer. I fully appreciate.
> >
> > And in a way I admit what you said,
> > but if you think of the command
> >
> > rsync -trvuz file.wrk uname at servername::uname-html
> >
> > what it does, then according to my logic
> >
> > rsync -trvuz -e ssh file.wrk uname at servername:uname-html
> >
> > should do exactly the same thing. Another thing would be
> > to say, that it originally is not realizable in this
> > way....
> > and why not?
>
> Because they don't say the same thing. in
> uname at servername::uname-html uname-html is a module which
> is explicitly defined as mapping to a directory. But in
> uname at servername:uname-html uname-html is just an ambiguous
> specification of a path, in this case relative to the home
> directory of the user uname.
>
> rsync needs to be able to sync a file with a file just like
> cp. This particular behavior is used quite frequently by
> people who explicitly rsync one file at a time inside
> scripts. The difference is that unlike cp rsync needs to
> behave deterministically. The result needs to be the same
> regardless of what exists at the destination prior to
> execution.
>
> The use of a trailing slash on a destination is a standard
> unix notation for "don't name it this but put it in the
> specified directory". That rsync supports this is to be
> expected and is much better than having to add an option.
>
> When you resync and the source has replaced a
> directory with a file rsync needs to delete the directory on
> the destination and copy the file that now exists on the
> source location.
>
> > Otherwise there is reconsideration of my perl
> > procedures not made by me. And same with the directories
> > that should only be known at the server side, not the
> > client
> > side, according to my logic. Perhaps I am wrong again,
> > but currently cannot understand why I should tell all the
> > clients if I want to change something in
> > the server. Using rsync again for this purpose, perhaps.
> > -All right, adding symbolic links to Linux and slashes
> > to the procedures.
> > But it is not that beautiful any more....-
> > I might do that, but currently I am not contented with the
> > nonsymmetric behaviour of rsync....I will start studying
> > port forwarding soon......and use rsync in that way if it
> > helps....
>
> The semantics of syncing with an rsync daemon vs. local or
> remote shell are very different such that the first path
> element given to the daemon is a module name, not a
> directory. A destination of
> uname at servername::modname/uname-html should have the same
> behavior pattern as uname at servername:uname-html
>
> It is a unclear to me what symlinks have to do with
> this. As for slashes, if a script breaks because of an
> unanticipated issue it needs to be updated.
>
> Most people scripting this would actually invoke it with
> rsync -trvuz -e ssh $srcdir/$file $user\@$server:$destdir/$file
> eliminating any ambiguity.
>
>
> --
> ________________________________________________________________
> J.W. Schultz Pegasystems Technologies
> email address: jw at pegasys.ws
>
> Remember Cernan and Schmitt
>
>
> --__--__--
>
> _______________________________________
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
>
> rsync mailing list
> rsync at lists.samba.org
> http://lists.samba.org/mailman/listinfo/rsync>
>
>
> End of rsync Digest
>
More information about the rsync
mailing list