Re: [PATCH] open O_TEXT and O_BINARY for cygwin/windows

2003-01-23 Thread Ville Herva
On Thu, Jan 23, 2003 at 01:55:40PM -0600, you [Dave Dykstra] wrote: > Why did you skip the fopen in log.c, which appends to the log file? I thought about that for a while. My reasoning was that the log file is probably read with unix/cygwin tools anyway - if not, the administrator is free to mount

Re: main.c error

2003-01-23 Thread jw schultz
On Thu, Jan 23, 2003 at 08:53:21PM -0600, Paul wrote: > Hello! This is not a real problem, since it seems to work correctly > anyway. But I'm still wondering about it. If I just execute "rsync" with > no switches or targets, it prints the usage, then gives an error at the > bottom: > > rsyn

main.c error

2003-01-23 Thread Paul
Hello! This is not a real problem, since it seems to work correctly anyway. But I'm still wondering about it. If I just execute "rsync" with no switches or targets, it prints the usage, then gives an error at the bottom: rsync error: syntax or usage error (code 1) at main.c(864) Is this nor

[patch] Still a problem with cleanup.c

2003-01-23 Thread Brian Poole
Hello, There is still a problem with the _exit_cleanup() function in cleanup.c despite the patch that was put in last week that prevented recursion. It turns out that sometimes multiple calls in close sequence are done and this causes rsync to spin out of control instead of exiting. This bug w

Resume not working

2003-01-23 Thread COFFMAN Steven
Title: Message Hi,     I ran out of disk space while getting ISOs doing: rsync -Pavz machinename::path/to/directory targetdir   When I deleted some stuff and used the same command to resume, I got an error (code 12) at io.c (165).   I had to delete the file in order to resume. Later, the co

aix 4.3 or 5

2003-01-23 Thread Patrick Amirian
Hi,   Where can I find rsync 2.5.5 for aix ? Thanks.

Re: Error message

2003-01-23 Thread Dave Dykstra
With file sizes over 2GB I'd suspect problems with >31-bit numbers being returned from stat() et. al. The rsync version you have on AIX is very old, and more recent versions handle large files better. The first thing to do is to upgrade rsync your AIX machine. - Dave On Thu, Jan 23, 2003 at 01:

how to send only the diff ?

2003-01-23 Thread Patrick Amirian
  Hi, I’m trying to do so that rsync does not send a file that exists but is different on the remote. I want rsync to send only the difference to the remote. I prefer to send the difference of a 500 MB file than sending the whole file over.   I use AIX and rsync version   rsync versi

Re: Rsyncing of block devices to a remote file

2003-01-23 Thread Dave Dykstra
I'm not sure why it would really need to know the size, but given that it wants it, can you open the file and lseek to the end of it? - Dave Dykstra On Thu, Jan 23, 2003 at 09:17:04AM +0100, David Heremans wrote: > Hello, > > I'm looking for some assistance in modifying the rsync code > > Situa

n00b needing help with rsync + win 9x

2003-01-23 Thread Linux Geek
hi, my first post here. i have knoppix linux 3.1 jan 01 release in iso format i want to update it to jan 20th release. i installed rsync for win 9x minimalist approach http://optics.ph.unimelb.edu.au/help/rsync/rsync_pc1.html command i used was : rsync246 -e ssh -avP rsync://ftp.gwdg.de/pub/

Re: [PATCH] open O_TEXT and O_BINARY for cygwin/windows

2003-01-23 Thread Dave Dykstra
Why did you skip the fopen in log.c, which appends to the log file? Because of the question about whether or not the "t" is ignored on all platforms, I'm a little nervous about putting this into 2.5.6. I don't have any problem with it for 2.6.0. Maybe it should be just in the 'patches' directory

how to send only the diff ?

2003-01-23 Thread Patrick Amirian
Hi, I’m trying to do so that rsync does not send a file that exists but is different on the remote. I want rsync to send only the difference to the remote. I prefer to send the difference of a 500 MB file than sending the whole file over.   I use AIX and rsync version   rsync version

Re: Please test rsync-2.5.6pre2

2003-01-23 Thread Dave Dykstra
On Tue, Jan 21, 2003 at 08:00:51PM -0801, Jos Backus wrote: > On Mon, Jan 20, 2003 at 10:19:42PM -0600, Dave Dykstra wrote: > > The second rsync-2.5.6 pre-release version is now available at: > > There's the popt-1.7 update (with Dave's sprintf() workaround) at > > http://www.catnook.com/patc

Re: send_files failed to open filename ...

2003-01-23 Thread Do-Risika RAFIEFERANTSIARONJY
jw schultz wrote: * is these messages harmful or not ? Not harmful. It is an indication of the volatility of the source at the time of transfer. Having some files disappear could result in an inconsistant state. For example: a web repository where the delete happens between index.html and g

SUMMARY: Error message

2003-01-23 Thread Boris Gegenheimer
I found the reason I think anyway. It was the different versions of rsync on the 2 machines. I upgraded the one on the AIX machine and then it copied just fine. Thank you jw and Michael for answering. Boris -Original Message- From: Michael Salmon [mailto:[EMAIL PROTECTED]] Sent: 23. jan

Re: send_files failed to open filename ...

2003-01-23 Thread jw schultz
On Thu, Jan 23, 2003 at 03:38:34PM +0300, Do-Risika RAFIEFERANTSIARONJY wrote: > > Hi everybody, > > I'm mirroring some websites with rsync (daemon on the source), and I > noticed in the destination host some error messages 'send_files failed > to open filenames', > > Actually, the concerned f

RE: Error message

2003-01-23 Thread Michael Salmon
On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer <[EMAIL PROTECTED]> wrote: +-- | The versions of the different machines I use are the initiating machine : | Sun 450 | Solaris 8 | Rsync 2.5.5 | | The machine that I try to copy from : | IBM rs6000 | AIX 4.3 | Rsync 2.3.1 | | Th

send_files failed to open filename ...

2003-01-23 Thread Do-Risika RAFIEFERANTSIARONJY
Hi everybody, I'm mirroring some websites with rsync (daemon on the source), and I noticed in the destination host some error messages 'send_files failed to open filenames', Actually, the concerned files are deleted on the source host, but I would like to ask : * why does rsync say these (in

Re: Error message

2003-01-23 Thread 'jw schultz'
On Thu, Jan 23, 2003 at 12:36:52PM +0100, Boris Gegenheimer wrote: > The versions of the different machines I use are the initiating machine : > Sun 450 > Solaris 8 > Rsync 2.5.5 > > The machine that I try to copy from : > IBM rs6000 > AIX 4.3 > Rsync 2.3.1 > > The command I use is > /usr/local

RE: Error message

2003-01-23 Thread Boris Gegenheimer
The versions of the different machines I use are the initiating machine : Sun 450 Solaris 8 Rsync 2.5.5 The machine that I try to copy from : IBM rs6000 AIX 4.3 Rsync 2.3.1 The command I use is /usr/local/bin/rsync -au -q --stats --progress --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 /dis

Re: Error message

2003-01-23 Thread jw schultz
On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: > Hello when i get this message what is wrong: > > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be > stored in data type > > Regards Boris Dunno. That error message is not in the rsync source. Since

Error message

2003-01-23 Thread Boris Gegenheimer
Title: Message Hello when i get this message what is wrong:   /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be stored in data type   Regards Boris

Re: Rsyncing of block devices to a remote file

2003-01-23 Thread jw schultz
On Thu, Jan 23, 2003 at 09:17:04AM +0100, David Heremans wrote: > Hello, > > I'm looking for some assistance in modifying the rsync code > > Situation: I used to back-up some of my (unmounted NTFS) disk partitions > remotely using the following shells construct: > dd if=/dev/hda1 | gzip | ssh me@

Rsyncing of block devices to a remote file

2003-01-23 Thread David Heremans
Title: Rsyncing of block devices to a remote file Hello, I'm looking for some assistance in modifying the rsync code Situation: I used to back-up some of my (unmounted NTFS) disk partitions remotely using the following shells construct: dd if=/dev/hda1 | gzip | ssh me@backupmachine 'cat >