rsync error: some files could not be transferred -- How to ignore

2008-04-09 Thread Kenneth Seal

Hi Wayne,

I read your thread online at http://lists.samba.org/archive/rsync/2005-June/012847.html 
 and I am having a similar problem.


In my case, rsync displays the error code "rsync error: some files  
could not be transferred (code 23)" and it kills my script. Do you  
have any advice on how would I go about writing, researching etc. a  
script to tell rsync to ignore such errors?


I am using the bash shell in Mac OS 10.5.2. Any help would be much  
appreciated.


Many thanks,
Ken
--
To unsubscribe or change options: https://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 -- How to ignore

2008-04-09 Thread Kyle Crawford


On Apr 8, 2008, at 11:27 PM, Kenneth Seal <[EMAIL PROTECTED]> wrote:


Hi Wayne,

I read your thread online at http://lists.samba.org/archive/rsync/2005-June/012847.html 
 and I am having a similar problem.


In my case, rsync displays the error code "rsync error: some files  
could not be transferred (code 23)" and it kills my script. Do you  
have any advice on how would I go about writing, researching etc. a  
script to tell rsync to ignore such errors?


I am using the bash shell in Mac OS 10.5.2. Any help would be much  
appreciated.


Many thanks,
Ken
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


The result code of a command is stored in a special variable named $?

Check the value of that variable in an if statement immediately after  
the rsync line in your script


If the value is 0 then there were no errors.  If the value is 23, then  
you could log a warning or not. If there is any other value in $? ,  
then you have another problem.


If we could see the relevant lines of your script we might be able to  
provide more help.


Also you control whether your script succeeds or fails based on the  
last line in your script.


If you want it to succeed, the last line would be

exit 0

Google for advanced bash scripting guide for more info.

Kyle
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


"set owner" option for rsync client

2008-04-09 Thread Corey Stup
I have the following configuration:

Server side:
rsync daemon running as suid root, use chroot set to false.

Client side:
rsync client setuid root (so that it can write over other suid root owned
files).

When doing a :: based rsync to the server, I'd like to have the client be
able to create/update files as the owner I pass on the command line.   Since
it has to be setuid root, and I don't use the -o option to preserve owner
(my users aren't the same between client and server so I don't want it to
map), it ends up creating the files as root.

There doesn't appear to be a way for me to tell rsync to use a specific
owner for creating/updating files.   The --chmod option lets me override
permissions, but nothing for owner.   Perhaps a --setuid option?

Any suggestions?
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

3.0.2 get_xattr_names on sockets?

2008-04-09 Thread Paul Reilly
Hello,

I've compiled a fresh copy of rsync 3.0.2 (version info below) on MacOSX Leopard
Server 10.5.1  and am doing an rsync of the whole system like this:

/bin/rsync302 -axX / /Volumes/appserv02/2008-14/ --exclude=/Network
--exclude=/net --exclude=/home

It works OK, but returns with a failure error code,
 and the following errors relating to files with sockets.

rsync: get_xattr_names:
llistxattr("private/etc/racoon/racoon.sock",1024) failed: Operation
not permitted (1)
 rsync: get_xattr_names:
llistxattr("private/etc/racoon/vpncontrol.sock",1024) failed:
Operation not permitted (1)
 rsync: get_xattr_names: llistxattr("private/tmp/ARD_ABJMMRT",1024)
failed: Operation not permitted (1)
 rsync error: some files could not be transferred (code 23) at
main.c(1031) [sender=3.0.2]



Is there any way to get rsync to ignore sockets like this, so the
backup with rsync
returns with a success status code?

My version is:

bash-3.2# ./rsync302 --version
rsync  version 3.0.2  protocol version 30
Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, no IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes


Thanks.

-- 
Paul Reilly
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


DO NOT REPLY [Bug 5381] New: make test fails without /etc/rsyncd.conf

2008-04-09 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=5381

   Summary: make test fails without /etc/rsyncd.conf
   Product: rsync
   Version: 3.0.2
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P3
 Component: core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
 QAContact: [EMAIL PROTECTED]


"make test" fails in >=3.0.1 when there is no /etc/rsyncd.conf. After "touch
/etc/rsyncd.conf" make test doesn't fail any more.

- daemon log follows
Testing for symlinks using 'test -h'
building configuration
/usr/src/RPM/BUILD/rsync-3.0.2/testtmp/daemon/test-rsyncd.conf
building help script /usr/src/RPM/BUILD/rsync-3.0.2/testtmp/daemon/ignore23
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(635)
[receiver=3.0.2]
- daemon log ends
FAILdaemon


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Lower-case filenames on receiver side

2008-04-09 Thread Marco Bridge

On 9 Apr, 2008, at 03:20 , Matt McCutchen wrote:

I would suggest tinkering with the "shortname" mount option of the FAT
partition and using the --ignore-case rsync option added by this  
patch:

http://rsync.samba.org/ftp/rsync/patches/ignore-case.diff


I tried to patch but that alone does not seem to do it.
I should try the shortname mount option but at the moment
i'd rather not play with that machine's mounts...
OS X does not seem to offer that option so i can't try with
my external drive (FAT32 too).

Is the --ignore-case option going to be included at some point in the  
future?


Thanks a lot for the help
Marco
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html