Re: RSync + SSH tunneling through firewall
Haai Andrzej, The problem is solved. When I double checked the ssh-b file I realized I had to change the linux commands to cygwin commands. >From that moment all commands (like date, hostname...) worked on the C-host So with the key authentification and the following ssh-b script: #!/bin/bash ssh [EMAIL PROTECTED] ssh "$@" the rsync command works: rsync -auv -e ~/ssh-b /cygdrive/driveletter/localfolder/ host_C:/cygdrive/driveletter/remotefolder and I don't get the pseudo terminal warning anymore. Whenever you are in Belgium, I owe you a beer or something else to drink. Thanx a lot for all the help. Kind regards, Stef Andrzej Filip wrote: Stefaan Lhermitte wrote: I did. I can now connect via SSH as wel from A - B as from B - C. I also resolved the problem of not being able to connect to C. I restarted the sshd and now it works. The problem now stays with the rsync. I used: rsync -auv -e ~/ssh-b /cygdrive/driveletter/localfolder/ computer-C:/cygdrive/driveletter/remotefolder/ I get no errors but only the following output: Pseudo-terminal will not be allocated because stdin is not a terminal. Unfortunately it does not rsynchronize, since no files are copied. 1) Do you get computer-C shell prompt when you execute "~/ssh-b computer-C" ? [ you may ignore "pseudo terminal warning in *this* test ] 2) What do you get when you execute "~/ssh-b computer-C date" ? [ Is date program executed on C ? ] -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1686] Could not transfer DBCS(Double byte Character set) filename
https://bugzilla.samba.org/show_bug.cgi?id=1686 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-09-09 01:37 --- We upgraded latest cygwin version(with cygwin DLL 1.5.11-1) and recompiled rsync on windows. And clear this problem. -- 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: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: RSync + SSH tunneling through firewall
Yessos, very cool. It works even with rsync -auv -e ssh [EMAIL PROTECTED] ssh src_folder host_C:sdt_dir Sometimes solutions can be very simple... Unfortunartely all open positions for email postmasters are just filled in. I did my best to convince my boss, you were better, but it didn't work.:) Thanx again! Stef Andrzej Filip wrote: It is nice to know it works [finally :) ]. As the last check try to eliminate ssh-b script and test rsync -auv -e ssh host_B ssh src_dir host_C:sdt_dir -- 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: Ownership
Rsync seems to work as if I had used the --numeric-ids If rsync doesn't find a username match, it will fall-back to using the ID directly, so I would assume that the problem is that the ID names on your cygwin system aren't matching the ID names on your linux system (and perhaps they aren't what you think). On the client side, under cygwin : ls -l = testdir owned by testuser:mkgroup_ ls -ln = testdir owned by 11385:10513 On the server side, under linux, with winbind running with winbind use default domain = yes, a directory on which I run chown testuser: dir becomes: ls -l = directory owned by testuser:'Domain user' (group translated from French) ls -ln = directory owned by 1:1 Knowing that gentent passwd | grep testuser shows: testuser:x:1:1:testuser:/home/DOMAIN/testuser:/bin/false When I set winbind use default domain = no, I get th following: DOMAIN\testuser:x:1:1:testuser:/home/DOMAIN/testuser:/bin/false But, in both case, after a rsync -avP testdir $BACKUPSERVER::backuptest I get testdir owned by 11385:10513, which are unknow user/group on the server. I had originally misread your question as one wanting to get the cygwin rsync to set ownership of the files. Towards this goal, I think we need a better am I root check for cygwin. The attached patch attempts to provide this. Is anyone familiar enough with cygwin to be able to comment on the appropriateness of this idiom? Why does the rsync running on the client must be root ? It just has to send the name of the owner of the file to the server which will chown it. And my server is running as root on the linux machine. Thank you for the time you already spent on my problem ! -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Bug in rsync? (--delete[-after])
Hello! I think I've found a bug in some (older) versions of rsync. The problem does not seem to have been reported at bugzilla. And of the 9 bugs found there by searching on --delete-after all have got the name [EMAIL PROTECTED] attached. I ask you therefore to check if this problem is found in the newest version of rsync as well! I've read the warnings at rsync.samba.org concering when and how to report bugs/postings to the rsync list. (It would have been a nice feature to be able to search the complete archive at http://lists.samba.org/archive/rsync/ for --delete-after) The problem is in short that rsync used with the option --delete-after does NOT delete older files rsynced, but --delete does. I choosed initially --delete-after to keep copies until all new files where copied so there should always be an online copy of the file. The versions I have used is, from [fra (no.)] hox /# rsync --version rsync version 2.5.5 protocol version 26 - and to [til (no.)]: hox /# ssh anvil rsync --version rsync version 2.6.2 protocol version 28 The newer command is on the machine hox: while read fra til; rsync -a -H -p -x --delete --exclude quota.user --exclude quota.group \ --rsync-path=/rsync $fra/ anvil:$til done /rsynke The old was the same, just with --delete-after and not --delete The datafile /rsynke: i# cat /rsynke /mn/hox/geofysikk /mn/anvil/geofysikk /mn/hox/u4 /mn/anvil/adm-u1 /mn/hox/u6 /mn/anvil/student-u2 /mn/hox/u1 /mn/anvil/ozon-u1 /mn/hox/u8 /mn/anvil/ozon-u2 /mn/hox/u11 /mn/anvil/dynmet-u3 /mn/hox/u10 /mn/anvil/ozon-u4 /mn/hox/student-u1 /mn/anvil/student-u1 /mn/hox/u5 /mn/anvil/hydro-u1 /mn/hox/u9 /mn/anvil/ozon-u3 /mn/hox/u7 /mn/anvil/dynmet-u2 /mn/hox/u2 /mn/anvil/osean-u1 /mn/hox/u3 /mn/anvil/dynmet-u1 /mn/hox/u12 /mn/anvil/slettes-u1 Here is a before and after status of the most troublesome disk; the first the from-disk and the last two the to-disk; of these the first by use of --delete-after and the last by use of --delete: hox /# df -h /mn/hox/u7 Filesystem SizeUsed Available Capacity Mounted enhalvtil#dynmet229G 23G 6003M80%/mn/hox/u7 hox /# ssh anvil df -h /mn/anvil/dynmet-u2 Filesystem Size Used Available Capacity tera3scsi#dynmet-u2 52G50G 2734M95%/mn/anvil/dynmet-u2 hox /# ssh anvil df -h /mn/anvil/dynmet-u2 FilesystemSize Used Available Capacity Mounted tera3scsi#dynmet-u252G 23G 30G44%/mn/anvil/dynmet-u2 As you can see --delte removed about 27G files on this filesystem alone. Regards, Kjell Andresen Systems administrator, University of Oslo, Norway Center for Information Technology Services and Department of Geosciences -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
ssh vs /sbin/nologin
If the shell of user alpha is /sbin/nologin When use rsync with ssh mode, is it possible for alpha to use rsync to backup data? I don't permit alpha to login the backup server. Thanks very much! Best Regards! Jacky Kim . -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
daemon mode vs remote shell mode
When use rsync with daemon mode, how to permit user from using rsync via remote shell mode? Thanks very much! Best Regards! Jacky Kim . -- 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 with ssh mode vs. chroot
When use rsync with daemon mode, rsync can call chroot. But with ssh mode, is it possible to use chroot? Thanks very much! Best Regards! Jacky Kim . -- 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: Ownership
On Wed, 8 Sep 2004, Wayne Davison wrote: On Wed, Sep 08, 2004 at 04:52:51PM -0400, Paul Haas wrote: I can think of 4 usefull modes: 1The default, don't try to chown(). 2 --ownerIf rsync thinks it is root, then try to chown() 3 --owner-whiningAlways try to chown() and whine if it doesn't work. 4 --owner-no-whining Always try to chown(), don't whine if it doesn't work. Here's a patch that adds mode 3 to the two existing modes (leaving mode 4 unimplemented for now). It forces the user to specify -oo to perform chowing even when not root (-ao is not enough), and to specify -gg to try to preserve all groups when not root (even if the group wasn't returned by the getgroups() call). For example: rsync -avoogg /src/ host:/dest This only works if both sides have this patch applied (otherwise the normal -o and -g behavior would apply). Thoughts? It looks good to me. You might want to add something like: --- options.c 2004-09-09 09:20:20.0 -0400 +++ options.c.new 2004-09-09 09:17:17.0 -0400 @@ -250,7 +250,9 @@ rprintf(F, -H, --hard-linkspreserve hard links\n); rprintf(F, -p, --perms preserve permissions\n); rprintf(F, -o, --owner preserve owner (root only)\n); + rprintf(F, -oo attempt to preserve owner (even if not root)\n); rprintf(F, -g, --group preserve group\n); + rprintf(F, -gg attempt to preserve group (even if not root)\n); rprintf(F, -D, --devices preserve devices (root only)\n); rprintf(F, -t, --times preserve times\n); rprintf(F, -S, --sparsehandle sparse files efficiently\n); Note: In a contrived test, rsync didn't do a chmod() after a chown() failed. So those files were left with the mode of the temporary file. I can't think of a real world situation where that matters. Now the stage is set for someone to create a filesystem with semantics that are designed for rsync. rsync wouldn't need to run as root on the system that holds the backups. FUSE, filesystem in userspace, is a good place to start. See http://lwn.net/Articles/68104 for a description. Note that an early version of FUSE had a bug such that any user could chown. Just call it a feature. .. wayne.. -- Paul Haas [EMAIL PROTECTED] -- 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 in rsync? (--delete[-after])
Kjell Andresen wrote: The problem is in short that rsync used with the option --delete-after does NOT delete older files rsynced, but --delete does. The versions I have used is, from [fra (no.)] hox /# rsync --version rsync version 2.5.5 protocol version 26 - and to [til (no.)]: hox /# ssh anvil rsync --version rsync version 2.6.2 protocol version 28 Does using both parameters --delete and --delete-after solve the problem? rsync only implies --delete when using --delete-after if you have rsync-2.5.6 or above. Regards, Stefan -- 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: Ownership
On Thu, Sep 09, 2004 at 11:46:48AM +0200, Essyug wrote: Why does the rsync running on the client must be root ? It just has to send the name of the owner of the file to the server which will chown it. I misread it as the receiver at first glance, thus the confusion. You're right that the sender doesn't need to be root. However, this topic split into a parallel topic of allowing a receiving rsync on cygwin to be able to chown files in order to try to solve that deficiency. ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
