DO NOT REPLY [Bug 5078] New: Unable to use Win32 device paths with --files-from
https://bugzilla.samba.org/show_bug.cgi?id=5078 Summary: Unable to use Win32 device paths with --files-from Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Windows XP Status: NEW Severity: major Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] I am using vshadow.exe to create a volume shadow copy of c: which is made available at //?/GLOBALROOT/Device/HarddiskVolumeShadowCopy1. I can then run the following rsync command succesfully: rsync -ae ssh //?/GLOBALROOT/Device/HarddiskVolumeShadowCopy1/SomeFolder/ [EMAIL PROTECTED]:Backup Next, I try to implement the same but using --files-from, as follows: rsync -ae ssh --files-from=files.txt //?/GLOBALROOT/Device/HarddiskVolumeShadowCopy1/ [EMAIL PROTECTED]:Backup (files.txt contains SomeFolder/) However, this fails with the following error: rsync: push_dir //?/GLOBALROOT/Device/HarddiskVolumeShadowCopy1/ failed: Not a directory (20) rsync error: errors selecting input/output files, dirs (code 3) at flist.c(1082) [sender=2.6.9] I have also tried without the trailing slash after HarddiskVolumeShadowCopy1 and get a different error: rsync: push_dir //?/GLOBALROOT/Device/HarddiskVolumeShadowCopy1 failed: Invalid argument (22) rsync error: errors selecting input/output files, dirs (code 3) at flist.c(1082) [sender=2.6.9] -- 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
rsync as daemon doesnt use secrets file but sshd
Hi all!
I have a problem configuring rsync as daemon:
This is my rsync.conf:
log file = /var/log/rsync.log
list = yes
uid = nobody
gid = nobody
secrets file = /etc/rsyncd.secrets
[section]
comment = Great stuff from remote.acme.com
path = /home/repos
auth users = marco
hosts allow = *
hosts deny = *
This is my /etc/rsyncd.secrets
marco:marco
This is the secrets file permission:
[EMAIL PROTECTED] marco]# ls -l /etc/rsyncd.secrets
-rw--- 1 root root 12 Nov 12 17:01 /etc/rsyncd.secrets
This is /etc/xinetd.d/rsync
service rsync
{
disable = no
socket_type = stream
wait= no
user= root
server = /usr/bin/rsync
server_args = --daemon
log_on_failure += USERID
}
The problem is that I can not rsync from a client: it seems rsync is using
pam and system users for logging. I've tried to enable the user marco as
system user and I can login!!! So I think rsync can not authenticate using
the secret file.
[EMAIL PROTECTED]:~$ rsync -vv [EMAIL PROTECTED]::section
opening connection using ssh -l marco server rsync --server --sender -vv .
FxS
[EMAIL PROTECTED]'s password:
Permission denied, please try again.
Into /var/log/messages I have
Nov 12 17:10:46 server sshd(pam_unix)[16221]: check pass; user unknown
Nov 12 17:10:46 server sshd(pam_unix)[16221]: authentication failure;
logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.0.34
What should I check?
Thanks
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
Re: rsync as daemon doesnt use secrets file but sshd
On Monday 12 November 2007 18:17, Marco Strullato wrote: snip [EMAIL PROTECTED]:~$ rsync -vv [EMAIL PROTECTED]::section opening connection using ssh -l marco server rsync --server --sender -vv . Is appears to be a client issue - where does it pick up the -e ssh from? Check for aliases in your shell or global client defaults for your distribution. The command feedback is as if you were including the -e ssh argument to rsync. Try: $ export LOGNAME=marco $ export RSYNC_PASSWORD=yourpassword $ mkdir tmp $ rsync -avv server::section tmp/ -A -- 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 as daemon doesnt use secrets file but sshd
On Mon, Nov 12, 2007 at 05:17:01PM +0100, Marco Strullato wrote: [EMAIL PROTECTED]:~$ rsync -vv [EMAIL PROTECTED]::section opening connection using ssh -l marco server rsync --server --sender -vv . This is incongruous. The first line has 2-colons (for daemon mode), but the connect line is connecting via ssh without the --daemon option, so rsync just saw a single colon. You should figure out why that colon disappeared. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync 3.0.0 pre5 + hard link preversation trigger assert
I've setup rsync 3.0.0 pre5 on distrib-coffee.ipsl.jussieu.fr (rsync server) and upload the same into mandriva cooker (development distribution). Someone reported this failure: rsync -auvPH --delete --exclude-from=/home/rfox/exclude.txt distrib-coffee.ipsl.jussieu.fr::mandrivalinux/devel/cooker/i586/ . receiving incremental file list rsync: hlink.c:253: check_prior: Assertion `(((unsigned char *)(node-data))[0]) != 0' failed. Aborted [EMAIL PROTECTED] cooker]$ cat /home/rfox/exclude.txt - media/debug_main/ - media/debug_contrib/ I was trying to see what happend (I am unable to reproduce) when I triggered this one: rsync -avPH -v distrib-coffee.ipsl.jussieu.fr::plf/ [...] rsync: hlink.c:130: match_gnums: Assertion `flist != ((void *)0)' failed. Abandon I don't plan to uninstall rsync 3.0 to fall back to 2.6.9, so feel free to use to test. Regards. signature.asc Description: This is a digitally signed message part. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
better rsync error code when no space?
Hi All I ran into this situation when rsync some files to remote side and remote file system run out of space. rsync: writefd_unbuffered failed to write 4 bytes [sender]: Connection reset by peer (104) rsync: write failed on /IMG_5106.JPG (in dest): No space left on device (28) no space was detected and reported. rsync error: error in file IO (code 11) at receiver.c(298) [receiver=3.0.0pre5] rsync: connection unexpectedly closed (27 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.0pre5] _exit_cleanup(code=12, file=io.c, line=601): about to call exit(12) looks like error code 12 is caused by first error, 104. shall rsync report ENOSPC for this? so it can be much easier to trace and find out the error. thanks! -- Ming Zhang @#$%^ purging memory... (*!% http://blackmagic02881.wordpress.com/ http://www.linkedin.com/in/blackmagic02881 -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--delete causes rsync failure
Hello, I just narrowed down an rsync command that keeps failing to the --delete flag: rsync -vv --delete --backup-dir=backup_target --archive /etc [EMAIL PROTECTED]: It gives the following output: ... backup_dir is --delete/ building file list ... done Invalid file index: 1868985864 (count=0) [receiver] delta-transmission enabled rsync error: protocol incompatibility (code 2) at sender.c(189) [receiver=2.6.9] rsync: connection unexpectedly closed (144421 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(458) [generator=2.6.9] rsync: connection unexpectedly closed (12 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(458) [sender=2.6.9] I have confirmed that the above rsync command causes the following to be excecuted on the server side: rsync --server -vvlogDtpr --backup-dir backup_target --delete . backup_target exists within the myuser account and has correct permissions. I find it odd that it says backup_dir is --delete/ when it isn't. I looked at the docs and they indicated that backup_dir is generally used with --backup (-b), but adding that doesn't help. The exact same command, without the --delete works correctly. And, if I switch --delete to --delete-after, everything works correctly. Ignoring the errors doesn't help either. Any ideas? Am I missing something in the docs? Is this a bug? Thanks for the help. --Kaleb -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
