RE: Help understanding rsync and cwrsync
Hi all, we are just beginning to dive into rsync. I have limited experience with just playing around with the examples and reading all the docs that I can. I just read an interesting post from a developer that mentions cwrsync is a minimalistic rsync and thus things like permissions are not transfered, the post was from 2004. Here are my questions I called cwrsync as minimalistic because it offers rsync functionality on cygwin only. A full-blown cygwin gives you an almost complete linux-like working environment. In all other aspects, cwrsync is same as rsync on cygwin. That applies also to issues around permissions. 1) Should we abandon cwrsync for cygwin + rsync? Have the disparities between the two versions been resolved? There are no disparities. Cwrsync and cygwin+rsync have the same behaviour, same executables and same dlls. 2) What are the risks with using cwrsync (we want a limited footprint on the client)? Rsync itself is a well-proven solution and is actively maintained. Cwrsync package has a very small footprint in comparison to the full cygwin and that reduces your vulnerability surface. - 3) Assuming we use straight cygwin + rsync how does the linux rsync server handle the permissions and ACL's of an NTFS files system? Are they restorable back to a windows machine? The linux server won't have any of the users plus the ACLS stuff is totally different that unix. I don't think that rsync on cygwin can be too much of help to address ACL-issues between unix and windows machines. You should experiment with following scenarios to find out what is actually possible to achieve: 1. Use rsync options -g -o -p (preserve group,ownership and permissions) 2a. Start rsync on windows after having 'CYGWIN=ntsec' set. That allows cygwin to map linux permissions to windows ones. NB! Try this in a test environment. You may end with a filesystem with permissions somewhat different than what you expect. 2b. Use 'CYGWIN=nontsec' instead. That's the recommended way for cwrsync users. No mapping occurs. Cwrsync package has a batch file example for it. Best regards Tev Cwrsync maintainer -- What profits a man if he gains the whole world yet loses his soul? -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- 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: Help understanding rsync and cwrsync
Thank you for your insight. It has been very beneficial!On 3/2/06, Tevfik Karagülle [EMAIL PROTECTED] wrote: Hi all,we are just beginning to dive into rsync. I have limited experience with just playing around with the examples and reading all the docs that I can.I just read an interesting post from a developer that mentions cwrsync is a minimalistic rsync and thus things like permissions are not transfered, the post was from 2004.Here are my questions I called cwrsync as minimalistic because it offers rsync functionality on cygwin only. A full-blowncygwin gives you an almost complete linux-like working environment. In all other aspects, cwrsync is same as rsync on cygwin. That applies also to issues around permissions. 1)Should we abandon cwrsync for cygwin + rsync?Have the disparities between the two versions been resolved?There are no disparities. Cwrsync and cygwin+rsync have the same behaviour, same executables and same dlls. 2)What are the risks with using cwrsync (we want a limited footprint on the client)?Rsync itself is a well-proven solution and is actively maintained. Cwrsync package has a very small footprint in comparison to the full cygwin and that reduces your vulnerability surface.- 3)Assuming we use straight cygwin + rsync how does the linux rsync server handle the permissions and ACL's of an NTFS files system?Are they restorable back to a windows machine?The linux server won't have any of the users plus the ACLS stuff is totally different that unix.I don't think that rsync on cygwin can be too much of help to address ACL-issues between unix and windows machines. You should experiment with following scenarios to find out what is actuallypossible to achieve:1. Use rsync options -g -o -p (preserve group,ownership and permissions)2a. Start rsync on windows after having 'CYGWIN=ntsec' set. That allows cygwin to map linux permissions to windows ones. NB! Try this in a test environment. You may end with a filesystem withpermissions somewhat different than what you expect.2b. Use 'CYGWIN=nontsec' instead. That's the recommended way for cwrsync users. No mapping occurs. Cwrsync package has a batch file example for it.Best regardsTevCwrsync maintainer -- What profits a man if he gains the whole world yet loses his soul? -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- What profits a man if he gains the whole world yet loses his soul? -- 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: Help understanding rsync and cwrsync
--- Doug Lochart [EMAIL PROTECTED] wrote: Windows (cw)Rsync Client -- Linux Rsync server 1) Should we abandon cwrsync for cygwin + rsync? Have the disparities between the two versions been resolved? I am using cwrsync and it runs fine connecting to Slackware server. 2) What are the risks with using cwrsync (we want a limited footprint on the client)? What risks? The footprint is small. 3) Assuming we use straight cygwin + rsync how does the linux rsync server handle the permissions and ACL's of an NTFS files system? Are they restorable back to a windows machine? The linux server won't have any of the users plus the ACLS stuff is totally different that unix. Can't say. I don't use cygwin. We will be using rsync over an SSH tunnel to start but will eventually switch to rsync over SSL. Why? What is wrong with SSH? I do not believe rsync supports SSL natively yet. We want to be able to add module definitions to the rsyncd.conf file as we go along without having to restart the rsync daemon or inetd service. We want this so that we can add new client machines without interfering with other clients use of the server. Is what we are trying to do workable? If so how should we run our rsync server. The config file containing the module settings is read by rsync at every connection so you do not need to restart the daemon. Alternatively, you can run rsyncd on a single-transfer basis. The remote user invokes the daemon. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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: Help understanding rsync and cwrsync
On 3/1/06, Peter [EMAIL PROTECTED] wrote: --- Doug Lochart [EMAIL PROTECTED] wrote: Windows (cw)Rsync Client -- Linux Rsync server 1) Should we abandon cwrsync for cygwin + rsync? Have the disparities between the two versions been resolved? I am using cwrsync and it runs fine connecting to Slackware server. I asked because in the mailing list archives I found this I want to make sure that cwRsync is NOT a separate product/solution or whatever. It is simply a packaging of rsync on cygwin to make deployment/installation easier. cwRsync is a minimalist environment and does not support keeping ownership information between transfers. It was posted by a cwrsync developer. We were having issues with file permissions not being transferred so this post caught my attention. It was dated in 2004 so I was wondering if this limitation still existes. I am not saying we did nothing wrong but it looks right and then I saw this post. So cwrsync works fine for you and you get all your permissions etc? 2) What are the risks with using cwrsync (we want a limited footprint on the client)? What risks? The footprint is small. I meant risks of cwrsync vs rsync over a full blown cygwin installation. Again I am asking this based on the post I found. I know the cwrsync footprint is small but a cygwn installation with rsync would be bigger. 3) Assuming we use straight cygwin + rsync how does the linux rsync server handle the permissions and ACL's of an NTFS files system? Are they restorable back to a windows machine? The linux server won't have any of the users plus the ACLS stuff is totally different that unix. Can't say. I don't use cygwin. Ok, how does cwrsync handle ACLs, users and permissions as on the windows box? How/where is that info kept in the filesystem on the linux box? Is it in meta-data? I figure basic file permissions are stored with the file but how is the user stored? I can't imagine we would have to create a user account for that end user ... or would we? We will be using rsync over an SSH tunnel to start but will eventually switch to rsync over SSL. Why? What is wrong with SSH? I do not believe rsync supports SSL natively yet. This will be deployed hopefully to many people. We feel that an SSL certificate would be easier than setting up seperate keys for each end user. The rsyncs would happen in nightly jobs without user intervention. We want to be able to add module definitions to the rsyncd.conf file as we go along without having to restart the rsync daemon or inetd service. We want this so that we can add new client machines without interfering with other clients use of the server. Is what we are trying to do workable? If so how should we run our rsync server. The config file containing the module settings is read by rsync at every connection so you do not need to restart the daemon. Alternatively, you can run rsyncd on a single-transfer basis. The remote user invokes the daemon. Could you explain how the last part works? (the remote user invokes the daemon)? Most examples I have seen mention running it in daemon mode or via inetd? Thanks again for your insite Doug __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- What profits a man if he gains the whole world yet loses his soul? -- 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: Help understanding rsync and cwrsync
--- Doug Lochart [EMAIL PROTECTED] wrote: Ok, how does cwrsync handle ACLs, users and permissions as on the windows box? How/where is that info kept in the filesystem on the linux box? Is it in meta-data? I figure basic file permissions are stored with the file but how is the user stored? I can't imagine we would have to create a user account for that end user ... or would we? I can get back to you later on this important question. I like to hear what others on this list are saying on this point. The config file containing the module settings is read by rsync at every connection so you do not need to restart the daemon. Alternatively, you can run rsyncd on a single-transfer basis. The remote user invokes the daemon. Could you explain how the last part works? (the remote user invokes the daemon)? Most examples I have seen mention running it in daemon mode or via inetd? On Windows box user invokes like this assuming src directory is on D: drive, rsync.exe -avr --rsh=ssh /cygdrive/d/src dir remote user@server::module --rsh is to specify encryption (optional). If you instead contact a standalone or inetd-awoken daemon then encryption is performed by default. The key for remote user invokes the daemon is the double colon followed by a module name. The user then supplies local password just as if he's logging in via SSH. In such case, single-transfer daemon is brought up and he checks user home directory for instructions (rsyncd.conf). To avoid a second (rsync) authentication do not use 'auth users' line in that file. This way each user has their own configuration. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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: Help understanding rsync and cwrsync
Hello Peter, Doug, On Wed, 1 Mar 2006 21:40:56 -0500 (EST) Peter [EMAIL PROTECTED] wrote: --- Doug Lochart [EMAIL PROTECTED] wrote: Windows (cw)Rsync Client -- Linux Rsync server 1) Should we abandon cwrsync for cygwin + rsync? Have the disparities between the two versions been resolved? I am using cwrsync and it runs fine connecting to Slackware server. [snip] Same here, no problem w/ cwrsync - rsync. BTW, I even use a minimalist Qt frontend: http://www.mollux.org/projects/rsbackup/. Regards, -- wwp signature.asc Description: PGP signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
