Re: cwRsync 2.5.7
Tev On Sunday 14 Dec 2003 11:36, Tevfik Karaglle wrote: I tried two snapshots from http://cygwin.com/snapshots : 20031214 and 20031206. The first one (14.dec) hangs all the time. The second one (06.dec) doesn't hang at all according to my tests!! I released an updated cwRsync package(1.0.3a) with the latter snapshot. It can be downloaded from http://itefix.no/cwrsync/cwRsync_1.0.3a_Installer.zip. It is definitely worth to test !! Yes, it does work for me too (cwRsync 1.1.0). Many thanks. ( I used the cygwin1.dll and rsync.exe from your package to replace the ones in my existing cygwin 1.5.5 installation.) ...John -- John Hunt Stokesley, N Yorks, UK e-mail: [EMAIL PROTECTED] URL: http://www.yoredale.uklinux.net/ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Bug on cygwin? (rsync 2.5.7v26, problem?)
On Saturday 20 Dec 2003 13:18, Douglas Beethe wrote: rsync -a xyz //somehost/abc # Source: WinXP, Target: Win2K I noticed the snippet in the above post using the // notation. Is that notation supposed to work? I came off the cygwin list where I reported a problem in running an rsync with the source being on a network path with the // notation. My only answer was someone mentioning that maybe rsync didn't support the // network notation (though I'm pretty sure I've used it on other occasions). I'd gotten the following errors: rsync -avv --progress //source/usr/src/packages/BUILD/dictd-1.4.9 /usr/src/packages/BUILD/ building file list ... expand file_list to 4000 bytes, did move 199 files to consider delta-transmission disabled for local transfer or --whole-file send_files failed to open //source/usr/src/packages/BUILD/dictd-1.4.9/ANNOUNCE: No such file or directory send_files failed to open //source/usr/src/packages/BUILD/dictd-1.4.9/COPYING: No such file or directory ...repeated for total of 193 filenames Then I tar'ed the files from the source to the dst to move them 'manually' and tried rerunning rsync -- wondering what it would do if all the files were already there and got: rsync -avv --progress //source/usr/src/packages/BUILD/dictd-1.4.9 /usr/src/packages/BUILD/ building file list ... expand file_list to 4000 bytes, did move 199 files to consider delta-transmission disabled for local transfer or --whole-file send_files failed to open //source/usr/src/packages/BUILD/dictd-1.4.9/ANNOUNCE: No such file or directory send_files failed to open //source/usr/src/packages/BUILD/dictd-1.4.9/ChangeLog: No such file or directory dictd-1.4.9/Makefile.conf is uptodate dictd-1.4.9/Makefile.in is uptodate send_files failed to open //source/usr/src/packages/BUILD/dictd-1.4.9/README: No such file or directory ...etc -- This time 85 files gave the error message...about half, I'd guess this was due to the FAT32 file-mod time, 2-second resolution problem -- the ones that didn't need transferring were readable on both src and target for comparing as uptodate, but any file that was thought to need transferring, couldn't be opened by the send_files call. I wonder if send_file is a supported system call on cygwin, or if it is if there might be a few kinks left in it? rsync version-info: rsync version 2.5.7 protocol version 26 Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 64-bit system inums, 64-bit internal inums Maybe it's specific to 2.5.7...dunno -linda -- --- Capitalism: The rewarding of software companies for producing software of the least quality the consumer will buy. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permissions Problems
Here's my command copied from a shell script:\ rsync --verbose --progress --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --links \ /home/* [EMAIL PROTECTED]:/remotebackups/ Here's some (a small part) of the output: jk/.recently-used 253 100%0.00kB/s0:00:00 rsync: recv_generator: mkdir jk/.secpanel/.runfiles: Permission denied (2) stat jk/.secpanel/.runfiles : Permission denied rsync: failed to open jk/.viminfo, continuing : Permission denied jk/.viminfo 4503 100%0.00kB/s0:00:00 rsync: recv_generator: mkdir jk/Desktop/Trash: Permission denied (2) stat jk/Desktop/Trash : Permission denied jk/rsync.sh 161 100%0.00kB/s0:00:00 mkstemp jk/..bash_history.zb2Vlp failed: Permission denied mkstemp jk/..fonts.cache-1.WRbevE failed: Permission denied mkstemp jk/..recently-used.rleTG4 failed: Permission denied mkstemp jk/..viminfo.IcFUcX failed: Permission denied mkstemp jk/.rsync.sh.focqIP failed: Permission denied rsync[17002] (sender) heap statistics: arena:1659224 (bytes from sbrk) ordblks: 51 (chunks not in use) smblks: 6 hblks: 1 (chunks from mmap) hblkhd:266240 (bytes from mmap) usmblks:0 fsmblks: 232 uordblks: 1509880 (bytes used) fordblks: 149344 (bytes free) keepcost: 132928 (bytes in releasable chunk) The script is being run from the root account. My understanding is that running as root will eliminate the permission errors, but apparently that's not so. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Permissions Problems
On Mon, Dec 22, 2003 at 11:45:50AM -0800, John Davis wrote: Here's my command copied from a shell script:\ rsync --verbose --progress --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --links \ /home/* [EMAIL PROTECTED]:/remotebackups/ Here's some (a small part) of the output: jk/.recently-used 253 100%0.00kB/s0:00:00 rsync: recv_generator: mkdir jk/.secpanel/.runfiles: Permission denied (2) stat jk/.secpanel/.runfiles : Permission denied rsync: failed to open jk/.viminfo, continuing : Permission denied jk/.viminfo 4503 100%0.00kB/s0:00:00 rsync: recv_generator: mkdir jk/Desktop/Trash: Permission denied (2) stat jk/Desktop/Trash : Permission denied jk/rsync.sh 161 100%0.00kB/s0:00:00 mkstemp jk/..bash_history.zb2Vlp failed: Permission denied mkstemp jk/..fonts.cache-1.WRbevE failed: Permission denied mkstemp jk/..recently-used.rleTG4 failed: Permission denied mkstemp jk/..viminfo.IcFUcX failed: Permission denied mkstemp jk/.rsync.sh.focqIP failed: Permission denied rsync[17002] (sender) heap statistics: arena:1659224 (bytes from sbrk) ordblks: 51 (chunks not in use) smblks: 6 hblks: 1 (chunks from mmap) hblkhd:266240 (bytes from mmap) usmblks:0 fsmblks: 232 uordblks: 1509880 (bytes used) fordblks: 149344 (bytes free) keepcost: 132928 (bytes in releasable chunk) The script is being run from the root account. My understanding is that running as root will eliminate the permission errors, but apparently that's not so. The permissions problems aren't local, they are on the remote server where you seem to be running as trt. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
getting rid of permission denied partial transfer errors
Hi, I am currently setting up a backup script for the /home directory of a server. I send all the files on a remote machine through LAN connection using rsync to optimize bandwidth usage. The script is run as root on the server by a cron job but rsync connects to the remote machine as a normal user via an ssh key certificate. This leads to many permission denied errors, as the server side can read files (as root), but cannot create them on the receiving side. rsync -azSHe ssh --delete --numeric-ids /home [EMAIL PROTECTED]:/mnt/backup/ Is there an option to ignore only such errors? I have read the man page over and over but i could not find anything to suit my needs. thanks -- Sayan -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: getting rid of permission denied partial transfer errors
sure avoid all perm/user issues by making the whole server suid. seen kids do that when they tired of having to su - root on their linux systems. The alternative would be to enable ssh for root for those particular cron jobs make sure the sshd_config is edited to disable this mischeif after the job has run and send and recieve as root on both ends, and set the proper rsync switch to retain onwers/perms . Thanks, Ron DuFresne Sayan wrote: Hi, I am currently setting up a backup script for the /home directory of a server. I send all the files on a remote machine through LAN connection using rsync to optimize bandwidth usage. The script is run as root on the server by a cron job but rsync connects to the remote machine as a normal user via an ssh key certificate. This leads to many permission denied errors, as the server side can read files (as root), but cannot create them on the receiving side. rsync -azSHe ssh --delete --numeric-ids /home [EMAIL PROTECTED]:/mnt/backup/ Is there an option to ignore only such errors? I have read the man page over and over but i could not find anything to suit my needs. thanks -- Ron DuFresne ITS Unix Group 919-871-6466 -- ITS policy requires the following notice: E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: getting rid of permission denied partial transfer errors
On Mon, Dec 22, 2003 at 09:11:26PM +0100, Sayan wrote: Hi, I am currently setting up a backup script for the /home directory of a server. I send all the files on a remote machine through LAN connection using rsync to optimize bandwidth usage. The script is run as root on the server by a cron job but rsync connects to the remote machine as a normal user via an ssh key certificate. This leads to many permission denied errors, as the server side can read files (as root), but cannot create them on the receiving side. rsync -azSHe ssh --delete --numeric-ids /home [EMAIL PROTECTED]:/mnt/backup/ Is there an option to ignore only such errors? I have read the man page over and over but i could not find anything to suit my needs. Strange clustering: two people with the same problem. Why ignore the errors? They are meaningfull unless you don't really care about whether the backups are any good. If you insist on doing it this way go to the backup server and chown the relevant file set to the account used. Then review your rsync arguments and eliminate any that are in conflict with running was a normal user: -a, -o, --numeric-ids, and probably -g -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: getting rid of permission denied partial transfer errors
Ron DuFresne wrote: sure avoid all perm/user issues by making the whole server suid. seen kids do that when they tired of having to su - root on their linux systems. this command is only one line extracted from a script. Syncing of other files require root privileges one the server side, eg squid logs. The alternative would be to enable ssh for root for those particular cron jobs make sure the sshd_config is edited to disable this mischeif after the job has run and send and recieve as root on both ends, and set the proper rsync switch to retain onwers/perms . i have tried to refrain from being root on both systems. ;-) The backup machine is quite paranoid, access is restricted by firewall filtering of the MAC/IP pairs. It would be quite disappointing to allow remote root access. I am having trouble with user/group matching, too, as a consequence. -- Sayan I am currently setting up a backup script for the /home directory of a server. I send all the files on a remote machine through LAN connection using rsync to optimize bandwidth usage. The script is run as root on the server by a cron job but rsync connects to the remote machine as a normal user via an ssh key certificate. This leads to many permission denied errors, as the server side can read files (as root), but cannot create them on the receiving side. rsync -azSHe ssh --delete --numeric-ids /home [EMAIL PROTECTED]:/mnt/backup/ Is there an option to ignore only such errors? I have read the man page over and over but i could not find anything to suit my needs. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: getting rid of permission denied partial transfer errors
On Mon, Dec 22, 2003 at 10:14:05PM +0100, Sayan wrote: Ron DuFresne wrote: sure avoid all perm/user issues by making the whole server suid. seen kids do that when they tired of having to su - root on their linux systems. this command is only one line extracted from a script. Syncing of other files require root privileges one the server side, eg squid logs. The alternative would be to enable ssh for root for those particular cron jobs make sure the sshd_config is edited to disable this mischeif after the job has run and send and recieve as root on both ends, and set the proper rsync switch to retain onwers/perms . i have tried to refrain from being root on both systems. ;-) The backup machine is quite paranoid, access is restricted by firewall filtering of the MAC/IP pairs. It would be quite disappointing to allow remote root access. I am having trouble with user/group matching, too, as a consequence. It is good for a backup server to be paranoid. That is why dirvish pulls. It is much harder to be secure and push. -- Sayan I am currently setting up a backup script for the /home directory of a server. I send all the files on a remote machine through LAN connection using rsync to optimize bandwidth usage. The script is run as root on the server by a cron job but rsync connects to the remote machine as a normal user via an ssh key certificate. This leads to many permission denied errors, as the server side can read files (as root), but cannot create them on the receiving side. rsync -azSHe ssh --delete --numeric-ids /home [EMAIL PROTECTED]:/mnt/backup/ Is there an option to ignore only such errors? I have read the man page over and over but i could not find anything to suit my needs. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: getting rid of permission denied partial transfer errors
jw schultz wrote: On Mon, Dec 22, 2003 at 09:11:26PM +0100, Sayan wrote: I am currently setting up a backup script for the /home directory of a server. I send all the files on a remote machine through LAN connection using rsync to optimize bandwidth usage. The script is run as root on the server by a cron job but rsync connects to the remote machine as a normal user via an ssh key certificate. This leads to many permission denied errors, as the server side can read files (as root), but cannot create them on the receiving side. rsync -azSHe ssh --delete --numeric-ids /home [EMAIL PROTECTED]:/mnt/backup/ Is there an option to ignore only such errors? I have read the man page over and over but i could not find anything to suit my needs. Why ignore the errors? They are meaningfull unless you don't really care about whether the backups are any good. I don't care if the backups of the users' homes are not perfect. Running as root on both sides is not an option, so there has to be limits anyway. Config files and logs are much more important, and backing up of the homes is bonus. As this command is run on a daily basis by a cron job, the same errors get reported every day. That's why i am looking for a way to suppress these particular error messages. (which i find perfectly normal btw) If you insist on doing it this way go to the backup server and chown the relevant file set to the account used. Then review your rsync arguments and eliminate any that are in conflict with running was a normal user: -a, -o, --numeric-ids, and probably -g That didn't solve the problem when i tested it some time ago. One failure example is trying to send files that cannot be written : Server side : dr--r--r-- my_directory dr--r--r-- my_directory\sample_file The rsync command tries to send sample_file to the backup server, which cannot write it because it was not able to recurse into my_directory. Removing the -p switch and removing the backup file did not succeed, and rsync continued to preserve the perms even without the switch. I am running rsync 2.5.5 on debian woody/stable. i have considered stripping the command down to the barest options (recursive compress and ssh) but the errors still get reported. -- Sayan -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Permissions Problems
Here's my command copied from a shell script:\ rsync --verbose --progress --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --links \ /home/* [EMAIL PROTECTED]:/remotebackups/ It looks like you don't have the --delete in there (which you should have to keep identical copies on both sides, but I don't know your situation so take that with a grain of salt), so based on that, I would guess you *might* have a full disk on the machine that you are backing up to. The script is being run from the root account. My understanding is that running as root will eliminate the permission errors, but apparently that's not so. You'll get the permission problems because a full disk will prevent you from adding anymore files onto it. -Chuck -- Quantum Linux Laboratories - ACCELERATING Business with Open Technology * Education | -=^ Ad Astra Per Aspera ^=- * Integration| http://www.quantumlinux.com * Support| [EMAIL PROTECTED] You know what you get after putting 30 years into a company? You're looking at it. -Downsized CIO of a major insurance carrier. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Permissions Problems
On Mon, Dec 22, 2003 at 02:16:21PM -0800, Chuck Wolber wrote: Here's my command copied from a shell script:\ rsync --verbose --progress --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --links \ /home/* [EMAIL PROTECTED]:/remotebackups/ It looks like you don't have the --delete in there (which you should have to keep identical copies on both sides, but I don't know your situation so take that with a grain of salt), so based on that, I would guess you *might* have a full disk on the machine that you are backing up to. The script is being run from the root account. My understanding is that running as root will eliminate the permission errors, but apparently that's not so. You'll get the permission problems because a full disk will prevent you from adding anymore files onto it. -Chuck Well, if you run one end as root and the other as non root user ([EMAIL PROTECTED] in your case) you may well have a problem with permissions. try making sure BOTH ends are root and then see if you still get the problems. Regards Tomasz Ciolek -- Tomasz M. Ciolek *** email: tmc at dreamcraft dot com dot au *** GPG Key ID: 0x41C4C2F0 Key available on www.pgp.net *** Everything falls under the law of change; Like a dream, a phantom, a bubble, a shadow, like dew or flash of lightning. You should contemplate like this. pgp0.pgp Description: PGP signature -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: Permissions Problems Problem solved!
I had forgotten to set the permissions on the upload folder on the remote server. Once I set the perms correctly, it worked. Thanks to everyone for the help! -Original Message- Here's my command copied from a shell script:\ rsync --verbose --progress --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --links \ /home/* [EMAIL PROTECTED]:/remotebackups/ Here's some (a small part) of the output: jk/.recently-used 253 100%0.00kB/s0:00:00 rsync: recv_generator: mkdir jk/.secpanel/.runfiles: Permission denied (2) stat jk/.secpanel/.runfiles : Permission denied rsync: failed to open jk/.viminfo, continuing : Permission denied jk/.viminfo 4503 100%0.00kB/s0:00:00 rsync: recv_generator: mkdir jk/Desktop/Trash: Permission denied (2) stat jk/Desktop/Trash : Permission denied jk/rsync.sh 161 100%0.00kB/s0:00:00 mkstemp jk/..bash_history.zb2Vlp failed: Permission denied mkstemp jk/..fonts.cache-1.WRbevE failed: Permission denied mkstemp jk/..recently-used.rleTG4 failed: Permission denied mkstemp jk/..viminfo.IcFUcX failed: Permission denied mkstemp jk/.rsync.sh.focqIP failed: Permission denied rsync[17002] (sender) heap statistics: arena:1659224 (bytes from sbrk) ordblks: 51 (chunks not in use) smblks: 6 hblks: 1 (chunks from mmap) hblkhd:266240 (bytes from mmap) usmblks:0 fsmblks: 232 uordblks: 1509880 (bytes used) fordblks: 149344 (bytes free) keepcost: 132928 (bytes in releasable chunk) The script is being run from the root account. My understanding is that running as root will eliminate the permission errors, but apparently that's not so. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Orphaned rsync process on remote machine?
All, Sometimes when I do an rsync, it times out and leaves on orphaned process on the remote machine. I am running rsync over ssh using public key authentication. I synchronize about twenty-five machines, and this problem only appears on one of them. It worked until recently on this machine. I don't know what changed or what is different. I run rsync with a command line like this (only the names have been changed to protect the innocent) :-): aa:msarrel /u/cas/msarrel 105 /usr/local/bin/rsync --verbose --checksum --recursive --copy-unsafe-links --times --rsh=ssh --rsync-path=/usr/local/bin/rsync --delete --timeout=90 --ignore-times --compress /lll/m/ [EMAIL PROTECTED]://iii/j/k building file list ... done io timeout after 90 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) aa:msarrel /u/cas/msarrel 106 I tried changing the timeout to be 300 seconds, but got the same result. To this particular machine, the packets actually take a fairly tortured route. They go from the source, out through a firewall, into a VPN tunnel, across the Internet, in through another firewall, out of the VPN tunnel, over the river, through the woods, to grandmother's house and finally to the destination machine. However, there is a second machine at the same site that works with the same tortured route. The orphaned process on the remote machine looks like this: 8 Rmsarrel 12023 12017 99 99 20 739adbf0471 01:25:32 ?2:44 /usr/local/bin/rsync --server 8 Smsarrel 12017 1 0 40 20 739a8740325 739e6d46 01:25:32 ?0:00 tcsh -c /usr/local/bin/rsync I'm using the following version of rsync: rsync version 2.5.6 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others http://rsync.samba.org/ Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 64-bit system inums, 64-bit internal inums rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Thanks, Marc -- Distributed Operations Coordinator | IO GDS System Engineer (Operations - Marc and Pam) | (Development - Marc) +1 818 393-7840 (voice) | +1 818 393-7786 (voice) +1 818 393-4669 (fax) | +1 818 393-4669 (fax) mailto:[EMAIL PROTECTED]| mailto:[EMAIL PROTECTED] +1 800 759- PIN 2028873 (pager) | +1 800 759- PIN 5877194 (pager) mailto:[EMAIL PROTECTED] (pager) | mailto:[EMAIL PROTECTED] (pager) Pager web message: http://www.skytel.com/servlet/SendMessage?pin=2028873pageme=yes (DOC's pager) http://www.skytel.com/servlet/SendMessage?pin=5877194pageme=yes (Marc's pager) https://cassini.jpl.nasa.gov/csos/io (IO home page) Jet Propulsion Laboratory 4800 Oak Grove Dr M/S 230-250 Pasadena, CA 91109-8099 U.S.A. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Orphaned rsync process on remote machine?
Upon further investigation, I think I found part of the problem. There was a weird circular link in the destination directory. I'm running a test of the fix right now. I ran a test with no --timeout option and that seemed to work. Then I found and deleted the circular link and am re-running with the normal 90-second time out. What should a normal time out be? Is 90 seconds too long? Too short? Thanks, Marc All, Sometimes when I do an rsync, it times out and leaves on orphaned process on the remote machine. I am running rsync over ssh using public key authentication. I synchronize about twenty-five machines, and this problem only appears on one of them. It worked until recently on this machine. I don't know what changed or what is different. I run rsync with a command line like this (only the names have been changed to protect the innocent) :-): aa:msarrel /u/cas/msarrel 105 /usr/local/bin/rsync --verbose --checksum --recursive --copy-unsafe-links --times --rsh=ssh --rsync-path=/usr/local/bin/rsync --delete --timeout=90 --ignore-times --compress /lll/m/ [EMAIL PROTECTED]://iii/j/k building file list ... done io timeout after 90 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) aa:msarrel /u/cas/msarrel 106 I tried changing the timeout to be 300 seconds, but got the same result. To this particular machine, the packets actually take a fairly tortured route. They go from the source, out through a firewall, into a VPN tunnel, across the Internet, in through another firewall, out of the VPN tunnel, over the river, through the woods, to grandmother's house and finally to the destination machine. However, there is a second machine at the same site that works with the same tortured route. The orphaned process on the remote machine looks like this: 8 Rmsarrel 12023 12017 99 99 20 739adbf0471 01:25:32 ?2:44 /usr/local/bin/rsync --server 8 Smsarrel 12017 1 0 40 20 739a8740325 739e6d46 01:25:32 ?0:00 tcsh -c /usr/local/bin/rsync I'm using the following version of rsync: rsync version 2.5.6 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others http://rsync.samba.org/ Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 64-bit system inums, 64-bit internal inums rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Thanks, Marc -- Distributed Operations Coordinator | IO GDS System Engineer (Operations - Marc and Pam) | (Development - Marc) +1 818 393-7840 (voice) | +1 818 393-7786 (voice) +1 818 393-4669 (fax) | +1 818 393-4669 (fax) mailto:[EMAIL PROTECTED]| mailto:[EMAIL PROTECTED] +1 800 759- PIN 2028873 (pager) | +1 800 759- PIN 5877194 (pager) mailto:[EMAIL PROTECTED] (pager) | mailto:[EMAIL PROTECTED] (pager) Pager web message: http://www.skytel.com/servlet/SendMessage?pin=2028873pageme=yes (DOC's pager) http://www.skytel.com/servlet/SendMessage?pin=5877194pageme=yes (Marc's pager) https://cassini.jpl.nasa.gov/csos/io (IO home page) Jet Propulsion Laboratory 4800 Oak Grove Dr M/S 230-250 Pasadena, CA 91109-8099 U.S.A. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync error: some files could not be transferred (code 23) at main.c(1045)
Hi! How can I find out what files wheren't transferred If I have error: rsync error: some files could not be transferred (code 23) at main.c(1045) running rsync? I've tried rsync -v[v][v] but had no success. It wasn't possible to make sure what where the files producing the error. Any idea? rsync is version 2.5.7 -- Thomas -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23) at main.c(1045)
On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED] wrote: Hi! How can I find out what files wheren't transferred If I have error: rsync error: some files could not be transferred (code 23) at main.c(1045) running rsync? I've tried rsync -v[v][v] but had no success. It wasn't possible to make sure what where the files producing the error. Any idea? rsync is version 2.5.7 You might try capturing stderr. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23) at main.c(1045)
On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED] wrote: Hi! How can I find out what files wheren't transferred If I have error: rsync error: some files could not be transferred (code 23) at main.c(1045) running rsync? I've tried rsync -v[v][v] but had no success. It wasn't possible to make sure what where the files producing the error. Any idea? rsync is version 2.5.7 You might try capturing stderr. Tried that too, but without success. The only message I see is IO error encountered - skipping file deletion rsync error: some files could not be transferred (code 23) at main.c(1045) May the file-list is getting a bit to big for rsync? If I splitt the transfer using for i in *; do rsync -avv --delete --delete-excluded server::public/$i dest/ done it works seamlessly. The file list is about 50 files long. -- Thomas -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
