(no subject)

2002-10-01 Thread
Title: MSN Home  

Re: --delete-after subtleties

2002-10-01 Thread Wayne Davison
On Tue, 1 Oct 2002, Nick Papadonis wrote: > [In 2.5.5] --delete-after [...] must be used with --delete to work. Unfortunately. In the current CVS version, however, --delete-after now implies --delete and the man page mentions this fact. So, this will work more logically whenever 2.5.6 gets rele

--delete-after subtleties

2002-10-01 Thread Nick Papadonis
rsync v2.5.5 x86 Linux This isn't documented, however --delete-after will perform that documented action. It must be used with --delete to work. I spent much time determining this subtle CLI usage. I would suggest either documenting --delete must be used with --delete-after . Alternatively, r

rsync hangs at the end of the work.

2002-10-01 Thread Pascal Bourguignon
Ok, so I tried with -v -v and -v -v -v, but this does not give more clue, only much more useless log data. I still have the problem that with: rsync -v -auxHS --delete --force / /backup/ I get the following log: building file list ... done deleting var/cache/man/cat1/gcc.1.gz

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread David Bigagli -Bokis-
Did you have a look at the core file? Building unstripped rsycn and then debug the core should give you some ideas. The large number you are getting may be caused by memory corruption. > Usually it's pretty obvious which environment variable is the problem. I think that you really mean process

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread Erik Enge
[EMAIL PROTECTED] writes: > Erik: One more thing to try: redirect in /dev/null to the rsync > command. At one time, at least, its behaviour was different based on > the nature of its STDIN. Make sure STDERR and STDIN are redirected > somewhere, too... either a file or null. All our output are r

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread tim . conway
Erik: One more thing to try: redirect in /dev/null to the rsync command. At one time, at least, its behaviour was different based on the nature of its STDIN. Make sure STDERR and STDIN are redirected somewhere, too... either a file or null. Some programs test their STDIO to see what environ

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread Erik Enge
Paul Haas <[EMAIL PROTECTED]> writes: > Then I run it once interactively and once through cron and compare stuff. > > Usually it's pretty obvious which environment variable is the problem. I also noticed in the logs that rsync exists with "exit code 12": Oct 1 01:31:59 backup-server inetd[1

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread Erik Enge
Paul Haas <[EMAIL PROTECTED]> writes: > This isn't specific to rsync. I must be missing something. The fact that rsync segfaults isn't specific to rsync? We run tens of thousands of cronjobs a week and none of them have so far segfaulted. However, since I can't make it segfault on the comma

Re: "error in rsync protocol data stream (code 12) at io.c(150)" revisited

2002-10-01 Thread Herta Van den Eynde
Bart Coninckx kindly pointed out my typo: the variable to define is RSYNC_RSH, and not RSYNC_SSH. Works fine now. Thanks for your assistance. Herta -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-

Re: "error in rsync protocol data stream (code 12) at io.c(150)" revisited

2002-10-01 Thread Herta Van den Eynde
Oops, I noticed I ran the command with the wrong rsync: Here's the proper error: bb> /usr/local/bin/rsync -a ccf.txt bbcom@tobias:/www2/virtualhosts/toledo/bbcom/ tobias.cc.kuleuven.ac.be: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync

"error in rsync protocol data stream (code 12) at io.c(150)" revisited

2002-10-01 Thread Herta Van den Eynde
I browsed the web and the archive, and apart from someone asking whether anyone else had rsync problems after installing OpenSSH 3.4, I came up empty. Can anyone point me in the right direction to debug this? I've got over 50 GB to keep in sync, and don't know of another elegant way to do it.

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread Paul Haas
On 1 Oct 2002, Erik Enge wrote: > Hi all. > > I have a script which I call from cron. It basically does some stopping > of a few services, rsyncs all files to a remote server and then starts > the services again. However, rsync segfaults: > > /share/bin/cron.root.backup.sh: line 28: 18453 Seg

Changing a directory to a symlink; rsync balks.

2002-10-01 Thread William Stearns
Good day, all, I'm using rsync 2.5.4 and a statically linked version of 2.5.5 to back up my main system to a backup drive (See rsync-backup at http://www.stearns.org/rsync-backup/ ). First, I made a full backup of the system. Then, on the main system, I merged the article

Re: rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread Trevor Marshall
Erik, 2.5.5 rsync crashes and burns my hard disk, you are indeed lucky to get a segmentation fault. When I reported flakiness I was told it was my hardware. I upgraded my hardware - no difference. Then I was told to change my 2.4.x kernel. Why? it runs everything else, and has reliably for over

rsync 2.5.5 segmentation fault on Linux x86.

2002-10-01 Thread Erik Enge
Hi all. I have a script which I call from cron. It basically does some stopping of a few services, rsyncs all files to a remote server and then starts the services again. However, rsync segfaults: /share/bin/cron.root.backup.sh: line 28: 18453 Segmentation fault rsync -acx --delete ${_