Is there a way to specify "strict modes = false" on the client side? I'm having trouble getting the client to accept the password file on Windows 2000, since rsync doesn't want the file to be other-readable, but this concept doesn't map too well to Windows. Alternatively, if I could simply set the proper permissions on the passfile, that would suit me fine, but it seems that although my Cygwin username is administrator, and I'm logged into Windows as the sole member of the administrators group, something is still awry. If I set the file permissions so that I can access it from within my Cygwin bash shell, rsync complains that it's world readable. The only way it doesn't complain about that is if it can't read it at all. Daemian Mack
Yeah, the windows ownerships/permissions thing. try adding this to your cygwin.bat file: set CYGWIN=ntea this lets it map ownerships and permissions more precisely. Note: any scripts you've written will still execute, but you won't be able to have them found by commandline completion until you manually set them executable. I had a pile of scripts that i was used to invoking with <firstletter><secondletter><TAB>. Which also didn't get them. I realized what it was, and fixed it. Tim Conway tim.conway@philips.com 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(nnnnnnnnnnnn, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me.... Tim?" "Mack, Daemian" <DMack@Tickets.com> Sent by: rsync-admin@lists.samba.org 02/11/2002 10:53 AM To: rsync@lists.samba.org cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject: Strict Mode for Client? Classification: Is there a way to specify "strict modes = false" on the client side? I'm having trouble getting the client to accept the password file on Windows 2000, since rsync doesn't want the file to be other-readable, but this concept doesn't map too well to Windows. Alternatively, if I could simply set the proper permissions on the passfile, that would suit me fine, but it seems that although my Cygwin username is administrator, and I'm logged into Windows as the sole member of the administrators group, something is still awry. If I set the file permissions so that I can access it from within my Cygwin bash shell, rsync complains that it's world readable. The only way it doesn't complain about that is if it can't read it at all. Daemian Mack
> Yeah, the windows ownerships/permissions thing. try adding > this to your > cygwin.bat file: > set CYGWIN=ntea > this lets it map ownerships and permissions more precisely. > Note: any > scripts you've written will still execute, but you won't be > able to have > them found by commandline completion until you manually set them > executable. I had a pile of scripts that i was used to invoking with > <firstletter><secondletter><TAB>. Which also didn't get > them. I realized > what it was, and fixed it.That worked beautifully; thank you! Daemian Mack
You're welcome. Note to users: I should have added this caveat. this works only on an NTFS volume. I'm not sure what happens with a FAT, but i know it wouldn't work. I just don't know if something worse than failure would happen. Tim Conway tim.conway@philips.com 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(nnnnnnnnnnnn, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me.... Tim?" "Mack, Daemian" <DMack@Tickets.com> 02/11/2002 12:14 PM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: rsync@lists.samba.org Subject: RE: Strict Mode for Client? Classification:> Yeah, the windows ownerships/permissions thing. try adding > this to your > cygwin.bat file: > set CYGWIN=ntea > this lets it map ownerships and permissions more precisely. > Note: any > scripts you've written will still execute, but you won't be > able to have > them found by commandline completion until you manually set them > executable. I had a pile of scripts that i was used to invoking with > <firstletter><secondletter><TAB>. Which also didn't get > them. I realized > what it was, and fixed it.That worked beautifully; thank you! Daemian Mack