Re: Corrupt images when transferring files from UNIX on Tandem with version 2.4.6

2000-11-29 Thread Brian Elliott Finley
Are both source and destination the same architecture? If not, and these are text files, ftp will do carriage return changes while rsync will not. -Brian Thus spake Mr. Ramon ([EMAIL PROTECTED]): > This one is weird one. I'm running UNIX rsync on Tandem (OSS) and it works > over rsh. Files

Re: Corrupt images when transferring files from UNIX on Tandem with version 2.4.6

2000-11-29 Thread Mike Lang
More specific... It was when rsyncing as root on an NFS mounted partition that wasn't exported for root access. Worked fine if the permissions were set read for everyone, which is they way it should have been since they were web pages. At 09:06 AM 11/28/00 -0700, Mike Lang wrote: >I have seen t

Re: Corrupt images when transferring files from UNIX on Tandem with version 2.4.6

2000-11-28 Thread Mike Lang
I have seen this when rsyncing files that didn't have proper read permission. They would be copied over as nulls. The files were on an NFS mounted partition. --Mike At 03:48 AM 11/28/00 -0500, Mr. Ramon wrote: >This one is weird one. I'm running UNIX rsync on Tandem (OSS) and it >work

Corrupt images when transferring files from UNIX on Tandem with version 2.4.6

2000-11-28 Thread Mr. Ramon
This one is weird one. I'm running UNIX rsync on Tandem (OSS) and it works over rsh. Files are being transferred from OSS (source) to my central server (dest) and byte counts match. When I try to open the file on the destination, I cannot see it. I get nulls when using vi. But if I ftp the