Re: using rsync to backup windows workstations
On Wednesday 14 Nov 01, Robert Scholten writes: For some help in getting started, see: http://optics.ph.unimelb.edu.au/help/rsync/rsync_user.html Unfortunately an irritating person at Redhat/cygwin insisted I remove my windoze binaries because I wasn't able to provide full source for cygwin and rsync. It's not always a pleasant job to enforce the GPL. But it's there for a reason. So here are some comments I send people that query me: a) rsync binaries for win32/cygwin are now available from the binaries section of the rsync web pages, maintained by someone at redhat I think b) the version attached is so old that you really shouldn't attempt to use it. Get the latest CVS version and add Wayne Davison's patches (see mailing list archives), in particular for use with Windoze systems, then compile it yourself with cygwin c) it's easy to compile under cygwin, and cygwin is easy to install, so I strongly recommend doing that d) also install openssh which compiles cleanly under cygwin and is much more reliable than the ssh that is attached here Both Robert and even Lapo fail to mention that a standard Cygwin installation already *includes* a working version of rsync! Just install Cygwin from http://cygwin.com/ and you're done. (It also already includes OpenSSH!) In fact Lapo is too modest, he's doing a fine enough job. The rsync shipped with Cygwin *does work*. I would go a bit further and publicly thank Lapo for his efforts. Cygwin users are very well served to have rsync distributed by default. Currently, Cygwin's setup program is deficient in that you have no guidance of which packages to install to get a working rsync-only installation, if all you want is rsync. At the moment, it's get everything, or you're on your own. That will change in the very near future. Hope this helps. Regards, David (Cygwin FAQ maintainer)
Re: using rsync to backup windows workstations
Hi David, et al, Cygwin is terrific, and appreciated by many, myself included. However, if all you want is rsync, cygwin is mighty cumbersome. My version of rsync required just a few files, which easily fit on a floppy, and all of which went into a single directory on the destination machine. This was appreciated by many of my colleagues that just wanted their machine backed up efficiently. While I appreciate the GPL, I don't think it makes much sense in this case. Why provide source to compile your own cygwin when it's publically available in many places already? Likewise for rsync. Who wants to compile their own cygwin DLL anyway? I didn't change the source, just packaged the binaries to make life easier for people that don't want to know the gritty details of cygwin and compiling rsync and don't want to go hunting all over the web to find the cygwin DLL, rsync binary, ssh binary, and a couple of documentation files. It all seems reminiscent of the heavy hand of Bill Gates, under the guise of open source. On Wed, 14 Nov 2001, David Starks-Browning wrote: On Wednesday 14 Nov 01, Robert Scholten writes: For some help in getting started, see: http://optics.ph.unimelb.edu.au/help/rsync/rsync_user.html Unfortunately an irritating person at Redhat/cygwin insisted I remove my windoze binaries because I wasn't able to provide full source for cygwin and rsync. It's not always a pleasant job to enforce the GPL. But it's there for a reason. So here are some comments I send people that query me: a) rsync binaries for win32/cygwin are now available from the binaries section of the rsync web pages, maintained by someone at redhat I think b) the version attached is so old that you really shouldn't attempt to use it. Get the latest CVS version and add Wayne Davison's patches (see mailing list archives), in particular for use with Windoze systems, then compile it yourself with cygwin c) it's easy to compile under cygwin, and cygwin is easy to install, so I strongly recommend doing that d) also install openssh which compiles cleanly under cygwin and is much more reliable than the ssh that is attached here Both Robert and even Lapo fail to mention that a standard Cygwin installation already *includes* a working version of rsync! Just install Cygwin from http://cygwin.com/ and you're done. (It also already includes OpenSSH!) In fact Lapo is too modest, he's doing a fine enough job. The rsync shipped with Cygwin *does work*. I would go a bit further and publicly thank Lapo for his efforts. Cygwin users are very well served to have rsync distributed by default. Currently, Cygwin's setup program is deficient in that you have no guidance of which packages to install to get a working rsync-only installation, if all you want is rsync. At the moment, it's get everything, or you're on your own. That will change in the very near future. Hope this helps. Regards, David (Cygwin FAQ maintainer) -- Robert Scholten Tel: +61 3 8344 5457 Mob: 0412 834 196 School of Physics Fax: +61 3 9347 4783 University of Melbourne email: [EMAIL PROTECTED] Victoria 3010 AUSTRALIA http://www.ph.unimelb.edu.au/~scholten
Re: using rsync to backup windows workstations
While I appreciate the GPL, I don't think it makes much sense in this case. Why provide source to compile your own cygwin when it's publically available in many places already? Likewise for rsync. Wasn't a simple hyperlink to the original sources on your page and in a README sufficient? After all everyone have some access to internet nowadays, having an URL is very much like having the file itself. Just my 2 cents, but I am no lawyer and cannot comprehend all the implications of GPL, tough I read it many times. A problem remains: wherever you have a full cygwin or not, you're usnig bash or not... you must use cygwin posix command line, so that using rsync alone is not that much a good idea IMHO... Go figure that C:\WinnT\sYsTem32 is called /cygdrive/c/WINTT/system32... At the moment, it's get everything, or you're on your own. That will change in the very near future. Anyway the new setup it under its way (setup has now a new mantainer, thanks Robert) and it WILL definitely support required packages for each package, so that an user that only needs rsync just selects rsync and it will auto-install zlib an all that is required (in fact I must install on a clean system to check what is actually needed just today). P.S.: maybe we are a bit too much off topic... -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
Re: using rsync to backup windows workstations
On Wednesday 14 Nov 01, Robert Scholten writes: Hi David, et al, My version of rsync required just a few files, which easily fit on a floppy, and all of which went into a single directory on the destination machine. This was appreciated by many of my colleagues that just wanted their machine backed up efficiently. I don't think anyone will come knocking on your door with handcuffs if you're making floppies for your colleagues. But when it's available for public consumption there are additional factors: 1. The GPL is the GPL. You can complain, but there it is. Sorry. 2. Cygwin behaves badly if there is more than one version of the cygwin DLL on your system. By distributing one and advising it goes in its own rsync directory, you create problems for them (and the Cygwin support mailing list) should they ever wish to use Cygwin for *anything* else but your own rsync distribution. You can support that (potential) problem for your colleagues, but who supports it for everyone else? That's my assessment, anyway. Cheers, David
Re: transfer interrupted (code20)
On Wed, Nov 14, 2001 at 11:05:55AM +0800, Michael P. Carel wrote: ... Hi, Im trying now to implement my mail server mirror but as i look at the logs of the mail server i used to mirror i see this type of log transfer interrupted (code20) at rsync.c(229). and it the remote who's mirrorring the mail server does not transferring file and got stocked in recieving file list. I've tried transffering other path and it works fine but in the users home directory im recieving this error. I have alot of users in my mail server. What seems to be the problem? I'm sorry, but that kind of problem is rather difficult to make a guess at remotely if we can't repeat the problem. Perhaps it might help if you told us your rsync version and operating system on both sides, but that probably won't be enough. You're going to have to do some further debugging yourself. Try narrowing it down to the smallest repeatable operation you can do to get the error message, and then use a system call tracer, a debugger, or added print statements in the code to try to focus in on the problem. In general transfer interrupted just means that a connection dropped prematurely for some unknown reason. - Dave Dykstra
Re: using rsync to backup windows workstations
I have about 12 NT servers that I want to backup 1 directory to my Linux Server. The problem I am having is trying to get it not to ask for the user's password. I am trying to use ssh. I just installed the latest cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was on the NT machine, I ran ssh-keygen (no passphrase) and then added the identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys. When I run: rsync -uv -e ssh *.* thomas@linuxbox:backup/ it asks for a password. Besides asking for the password, it works fine. Only the files changed are updated and it is FAST! I saw the ssh-agent. Do I need to use it? and how? Is there something I need to do on my Linux server? I am pretty new to Linux, and have a long way to go to be an expert, but I can get around. Thanks for any help. Thomas Lambert VP DSC Associates, Inc. [EMAIL PROTECTED] - Original Message - From: Lapo Luchini [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 13, 2001 5:23 PM Subject: Re: using rsync to backup windows workstations As officially I'm the mantainer of cygwin's rsync package I feel I must add something.. 0=) a) rsync binaries for win32/cygwin are now available from the binaries section of the rsync web pages, maintained by someone at redhat I think Maintained by me, I don't work for redhat, and sadly I have a bit too little time to maintain it as I should... b) the version attached is so old that you really shouldn't attempt to use it. Get the latest CVS version and add Wayne Davison's patches (see mailing list archives), in particular for use with Windoze systems, then compile it yourself with cygwin ...but not so little not to compile it with Wayne's patches (actual patch is the latest anti-hang available at the date of the release of cygwin's rsync-2.4.6-2 package) ;-) If there's some patch that I missed (I read this mailing list since when I began to mantain that package, but reading only headers of most messages maybe I missed something...) please point it to me and I'll release a new verison shortly =) Please note that I'm not an expert programmer of rsync, just a person that likes and uses it (and wants maybe to become such an expert, btw): in cygwin one package can't exist in the distribution if there's not a mantainer... so I hope that the effort I put in it is not wasted, even if it's maybe not enough... [I've got a bit of guild for that eheh] c) it's easy to compile under cygwin, and cygwin is easy to install, so I strongly recommend doing that That's true, it compiles out-of-the box. The main problem is that in winsocks if the socket is closed a RST is sent, not flushing the cache. This creates many errors at the end of trasnfer, especially in the daemon mode (which is not addressed by the patch I used, I bet). d) also install openssh which compiles cleanly under cygwin and is much more reliable than the ssh that is attached here Compiles cleanly and is available as a binary. If anyone wants to ask some more question.. feel free, even if I don't know nothing special about it, as I said I had not had the time to completely study and understand rsync source... C ya, Lapo -- Lapo Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
Any Idiots guides out there
Hi there, I need to set-up something to syncronise (say every hour) a set of ftp and config files between two servers and rsync seems to be the prog for the job (for a HA ftp server using Pro-ftp). But so far, unless i run as root, with root being able to login to both servers, it doesn't work. I get the feeling i'm getting confused with rsh and ssh setups and bitshence an idiots guid to getting the job done would be a life saver Any pointers ??? Ta, Lee -- Lee Edward Armstrong (now in maried form!)http://www.darkwave.org.uk/~lee My Clothes Will Impress You, And My Claws Will Undress You. - The Damned
Re[2]: using rsync to backup windows workstations
Thomas Lambert [EMAIL PROTECTED] wrote: I have about 12 NT servers that I want to backup 1 directory to my Linux Server. The problem I am having is trying to get it not to ask for the user's password. I am trying to use ssh. I just installed the latest cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was on the NT machine, I ran ssh-keygen (no passphrase) and then added the identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys. When I run: rsync -uv -e ssh *.* thomas@linuxbox:backup/ it asks for a password. Well, first dumb question - are the versions of ssh the same? Is the sshd set up to allow null passwords during login? Also, I *think* you'll need 'RSAAuthentication yes'. (I also have PasswordAuthentication yes, PermitEmptyPasswords no Really dumb question - whats the permisison on authorized_keys? (Mine is 644) My authorized_keys file has, at the end, 'rcarruth@msfree', which is the userid and machine from which I do ssh stuff to the machine that allows it (with no password, see, it really does work: rcarruth@msfree scp rusty@foo:/home/rusty/sap\* /export/home/oodclass.etc saphhire-supper-001.jpg 100% || 408 KB00:01 But this is from a Solaris machine (msfree) to a linux machine (foo). I don't know if that matters, but it might. Besides asking for the password, it works fine. Only the files changed are updated and it is FAST! I saw the ssh-agent. Do I need to use it? maybe, but lets see if you can get away without it first. First, let me say that I don't know much (anything?) about cygwin. But I don't think that's the problem anyway, so I'll stick my foot in my mouth and proceed ;-) and how? Is there something I need to do on my Linux server? I am pretty new to Linux, and have a long way to go to be an expert, but I can get around. Don't worry about it, an expert is just a drip under pressure anyway ;-) rc
Re: using rsync to backup windows workstations
Im guessing it's in /etc/sshd_config. ssh issue, not rsync. try ssh linuxbox uname -a from a windoze machine. if that doesn't work without a password, neither will rsync. From man sshd: +++ PasswordAuthentication Specifies whether password authentication is allowed. The de- fault is ``yes''. Note that this option applies to both protocol versions 1 and 2. PermitEmptyPasswords When password authentication is allowed, it specifies whether the server allows login to accounts with empty password strings. The default is ``no''. +++ If PasswordAuthentication is yes, then you'll need to ensure that PermitEmptyPasswords is also yes, or you won't be allowed passphraseless authentication. If you're not permitted to change that, just use a simple ssh passphrase. From man rsync: +++ Some paths on the remote server may require authentication. If so then you will receive a password prompt when you con- nect. You can avoid the password prompt by setting the environment variable RSYNC_PASSWORD to the password you want to use or using the --password-file option. This may be use- ful when scripting rsync. +++ Wonderful thing, those man pages. Good luck. Tim Conway [EMAIL PROTECTED] 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(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), .\n ' There are some who call me Tim? Thomas Lambert [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 11/14/2001 08:15 AM To: [EMAIL PROTECTED] cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject:Re: using rsync to backup windows workstations Classification: I have about 12 NT servers that I want to backup 1 directory to my Linux Server. The problem I am having is trying to get it not to ask for the user's password. I am trying to use ssh. I just installed the latest cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was on the NT machine, I ran ssh-keygen (no passphrase) and then added the identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys. When I run: rsync -uv -e ssh *.* thomas@linuxbox:backup/ it asks for a password. Besides asking for the password, it works fine. Only the files changed are updated and it is FAST! I saw the ssh-agent. Do I need to use it? and how? Is there something I need to do on my Linux server? I am pretty new to Linux, and have a long way to go to be an expert, but I can get around. Thanks for any help. Thomas Lambert VP DSC Associates, Inc. [EMAIL PROTECTED] - Original Message - From: Lapo Luchini [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 13, 2001 5:23 PM Subject: Re: using rsync to backup windows workstations As officially I'm the mantainer of cygwin's rsync package I feel I must add something.. 0=) a) rsync binaries for win32/cygwin are now available from the binaries section of the rsync web pages, maintained by someone at redhat I think Maintained by me, I don't work for redhat, and sadly I have a bit too little time to maintain it as I should... b) the version attached is so old that you really shouldn't attempt to use it. Get the latest CVS version and add Wayne Davison's patches (see mailing list archives), in particular for use with Windoze systems, then compile it yourself with cygwin ...but not so little not to compile it with Wayne's patches (actual patch is the latest anti-hang available at the date of the release of cygwin's rsync-2.4.6-2 package) ;-) If there's some patch that I missed (I read this mailing list since when I began to mantain that package, but reading only headers of most messages maybe I missed something...) please point it to me and I'll release a new verison shortly =) Please note that I'm not an expert programmer of rsync, just a person that likes and uses it (and wants maybe to become such an expert, btw): in cygwin one package can't exist in the distribution if there's not a mantainer... so I hope that the effort I put in it is not wasted, even if it's maybe not enough... [I've got a bit of guild for that eheh] c) it's easy to compile under cygwin, and cygwin is easy to install, so I strongly recommend doing that That's true, it compiles out-of-the box. The main problem is that in winsocks if the socket is closed a RST is sent, not flushing the cache. This creates many errors at the end of trasnfer, especially in the daemon mode (which is not addressed by the patch I used, I bet).
Re: using rsync to backup windows workstations
On Wed, Nov 14, 2001 at 10:12:27AM -0700, [EMAIL PROTECTED] wrote: OK, I might be actually getting this. Here is part of my sshd_config file ... # To disable tunneled clear text passwords, change to no here! PasswordAuthentication yes PermitEmptyPasswords no this REQUIRES that a password be used, No it does not. It only makes password authentication one of the options and when it is used, the password can't be empty. # Comment to enable s/key passwords or PAM interactive authentication # NB. Neither of these are compiled in by default. Please read the # notes in the sshd(8) manpage before enabling this on a PAM system. ChallengeResponseAuthentication no Do I just need to change the last line to yes (ChallengeResponseAuthentication yes) and then when I generate my key on the NT box, put in a passphrase. No, ChallengeResponse is a totally different kind of authentication method. +++ If PasswordAuthentication is yes, then you'll need to ensure that PermitEmptyPasswords is also yes, or you won't be allowed passphraseless authentication. WRONG. Passwords have nothing to do with passphrases. To: [EMAIL PROTECTED] cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject:Re: using rsync to backup windows workstations Classification: I have about 12 NT servers that I want to backup 1 directory to my Linux Server. The problem I am having is trying to get it not to ask for the user's password. I am trying to use ssh. I just installed the latest cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was on the NT machine, I ran ssh-keygen (no passphrase) and then added the identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys. When I run: rsync -uv -e ssh *.* thomas@linuxbox:backup/ it asks for a password. Besides asking for the password, it works fine. Only the files changed are updated and it is FAST! I saw the ssh-agent. Do I need to use it? and how? Is there something I need to do on my Linux server? I am pretty new to Linux, and have a long way to go to be an expert, but I can get around. The problem is probably that it's defaulting to use ssh protocol 2, and and ssh-keygen defaults to makeing a key for protocol 1. If you either run 'ssh -1' or start over with an 'ssh-keygen -t rsa' you should be ok. Use ssh -v verbose mode to find out for sure what's going on. You may also have permissions problems on the server; it requires that all files and parent directories not be world readable. - Dave Dykstra
Re: Any Idiots guides out there
Hiya, I get the feeling i'm getting confused with rsh and ssh setups and bitshence an idiots guid to getting the job done would be a life saver Ignore thisI've now got something roughly going. I was quite confused between using rsync with rsh/ssh and using the daemon mode, the difference being the client side with an extra : eg rsync -avz [EMAIL PROTECTED]::ftp /home/proftp/ Also i was having problems as my rsync.conf had [ftp file] as I thought the stuff in the brackets was a nominal name rather than an actual module name Oh and theres a useful guide at http://www.freebsddiary.org/rsync.php Ta, Lee -- Lee Edward Armstrong (now in maried form!)http://www.darkwave.org.uk/~lee My Clothes Will Impress You, And My Claws Will Undress You. - The Damned
Re: rsync: Re: using rsync to backup windows workstations
On Wed, Nov 14, 2001 at 10:15:59AM -0500, Thomas Lambert wrote: I have about 12 NT servers that I want to backup 1 directory to my Linux Server. The problem I am having is trying to get it not to ask for the user's password. I am trying to use ssh. I just installed the latest cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was on the NT machine, I ran ssh-keygen (no passphrase) and then added the identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys. Instead of using ssh, why don't you use straight rsync, with rsync running in server mode on the Linux box. You should probably put separate entries in /etc/rsyncd.conf for each Windows box something like the one below that I use to backup our local hardware suffering from the Microsoft Virus, W2K. [dumbo_backup] uid = root gid = root path = /rd0/backups/dumbo read only = false use chroot = false comment = Backup for Dumbo Win2K hosts allow = 192.168.253.28 hosts deny = * Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ Breathe fire, slay dragons, and take chances. Failure is temporary, regret is eternal.
Re: rsync: Re: using rsync to backup windows workstations
I thought just a straight rsync daemon was unsecure. I am sending data from remote dial-up sites, through the internet to my server. That is why I am using ssh (well trying to use it). If this was just for my internal network, then YES, I would probably just use the daemon. One other problem is that they are dial-up, so each time they connect to the internet, they get a new IP. I tried just doing ssh linuxbox username -a and I was asked for a password. So I changed PasswordAuthentication to no in my sshd_config file on the server. Restarted sshd and now I am getting permission denied. I did copy the contents of my identity.pub, rsa_id.pub, dsa_id.pub to authorized_keys on the server. I'm going to read some more on ssh, but if anyone knows a quick fix, let me know. - Original Message - From: Bill Campbell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 14, 2001 2:45 PM Subject: Re: rsync: Re: using rsync to backup windows workstations On Wed, Nov 14, 2001 at 10:15:59AM -0500, Thomas Lambert wrote: I have about 12 NT servers that I want to backup 1 directory to my Linux Server. The problem I am having is trying to get it not to ask for the user's password. I am trying to use ssh. I just installed the latest cygwin on my NT server (1.3.4). Rsync is 2.4.6. What I have tried was on the NT machine, I ran ssh-keygen (no passphrase) and then added the identity.pub to the Linux box in the /home/thomas/.ssh/authorized_keys. Instead of using ssh, why don't you use straight rsync, with rsync running in server mode on the Linux box. You should probably put separate entries in /etc/rsyncd.conf for each Windows box something like the one below that I use to backup our local hardware suffering from the Microsoft Virus, W2K. [dumbo_backup] uid = root gid = root path = /rd0/backups/dumbo read only = false use chroot = false comment = Backup for Dumbo Win2K hosts allow = 192.168.253.28 hosts deny = * Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ Breathe fire, slay dragons, and take chances. Failure is temporary, regret is eternal.
Re: rsync: Re: using rsync to backup windows workstations
On Wed, 2001-11-14 at 14:35, Thomas Lambert wrote: I thought just a straight rsync daemon was unsecure. I am sending data from remote dial-up sites, through the internet to my server. That is why I am using ssh (well trying to use it). If this was just for my internal network, then YES, I would probably just use the daemon. One other problem is that they are dial-up, so each time they connect to the internet, they get a new IP. You are right: Rsync as a daemon in your environment would be less secure than ssh. I tried just doing ssh linuxbox username -a and I was asked for a password. So I changed PasswordAuthentication to no in my sshd_config file on the server. Restarted sshd and now I am getting permission denied. I did copy the contents of my identity.pub, rsa_id.pub, dsa_id.pub to authorized_keys on the server. I'm going to read some more on ssh, but if anyone knows a quick fix, let me know. There are two: make sure the dsa_id.pub is in authorized_keys2 if you just use '-e ssh' as an option for rsync, this automagically uses ssh version 2, so you need the '2' you keys file. 'authorized_keys' is for ssh 1. You can change the -e option to -e 'ssh 1' to use auhtorized_keys (I believe that is the command line; I got ssh 1 doing authentication but I switched to 2 because it is much more secure). Ben Ricker System Administrator Wellinx.com
Re: rsync: Re: using rsync to backup windows workstations
THAT WAS IT!! I just had authorized_keys and not authorized_keys2. I knew I had to be close. THANK YOU! THANK YOU! THANK YOU! - Original Message - From: Ben Ricker [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 14, 2001 3:47 PM Subject: Re: rsync: Re: using rsync to backup windows workstations On Wed, 2001-11-14 at 14:35, Thomas Lambert wrote: I thought just a straight rsync daemon was unsecure. I am sending data from remote dial-up sites, through the internet to my server. That is why I am using ssh (well trying to use it). If this was just for my internal network, then YES, I would probably just use the daemon. One other problem is that they are dial-up, so each time they connect to the internet, they get a new IP. You are right: Rsync as a daemon in your environment would be less secure than ssh. I tried just doing ssh linuxbox username -a and I was asked for a password. So I changed PasswordAuthentication to no in my sshd_config file on the server. Restarted sshd and now I am getting permission denied. I did copy the contents of my identity.pub, rsa_id.pub, dsa_id.pub to authorized_keys on the server. I'm going to read some more on ssh, but if anyone knows a quick fix, let me know. There are two: make sure the dsa_id.pub is in authorized_keys2 if you just use '-e ssh' as an option for rsync, this automagically uses ssh version 2, so you need the '2' you keys file. 'authorized_keys' is for ssh 1. You can change the -e option to -e 'ssh 1' to use auhtorized_keys (I believe that is the command line; I got ssh 1 doing authentication but I switched to 2 because it is much more secure). Ben Ricker System Administrator Wellinx.com
Re: rsync: Re: using rsync to backup windows workstations
On Wed, Nov 14, 2001 at 02:47:42PM -0600, Ben Ricker wrote: On Wed, 2001-11-14 at 14:35, Thomas Lambert wrote: I thought just a straight rsync daemon was unsecure. I am sending data from remote dial-up sites, through the internet to my server. That is why I am using ssh (well trying to use it). If this was just for my internal network, then YES, I would probably just use the daemon. One other problem is that they are dial-up, so each time they connect to the internet, they get a new IP. You are right: Rsync as a daemon in your environment would be less secure than ssh. Agreed. I tried just doing ssh linuxbox username -a and I was asked for a password. So I changed PasswordAuthentication to no in my sshd_config file on the server. Restarted sshd and now I am getting permission denied. I did copy the contents of my identity.pub, rsa_id.pub, dsa_id.pub to authorized_keys on the server. I'm going to read some more on ssh, but if anyone knows a quick fix, let me know. There are two: make sure the dsa_id.pub is in authorized_keys2 if you just use '-e ssh' as an option for rsync, this automagically uses ssh version 2, so you need the '2' you keys file. 'authorized_keys' is for ssh 1. You can change the -e option to -e 'ssh 1' to use auhtorized_keys (I believe that is the command line; I got ssh 1 doing authentication but I switched to 2 because it is much more secure). Not anymore in OpenSSH 3.0p1: the regular known_hosts and authorized_keys files hold both kinds of keys, and the *2 files are deprecated. He's using cygwin 1.3.4 which includes OpenSSH 3.0p1. - Dave Dykstra
Re: rsync: Re: using rsync to backup windows workstations
On Wed, Nov 14, 2001 at 04:23:32PM -0500, Thomas Lambert wrote: THAT WAS IT!! I just had authorized_keys and not authorized_keys2. I knew I had to be close. THANK YOU! THANK YOU! THANK YOU! Then your server just be older than openssh 3.0. Right? - Dave Dykstra
my rsyncs *do* exit, if I don't use -v
If I use -v or -vv, the rsyncs will hang forever (or at least a few days, I haven't let them run any longer than that so I'm nto sure if they'd eventually exit on their own or not). The information on rsync and OS version was sent in my previous email. For now i'm just going to run without -v, as I need to get this going and don't have time to get intimately involved with rsync. But if someone's heard of this before and/or is working on this bug (i assume it's a bug?), and you need mroe info from me, let me know if there's anything I can do. --jessica
Re: my rsyncs *do* exit, if I don't use -v
What is holding up 2.4.7? 2.4.6 frequently has these hang problems that are fixed in the cvs tree. But linux distros keep shipping 2.4.6 and users keep having troubles. I think we need to release a rsync 2.4.7. eric Jessica Koeppel wrote: If I use -v or -vv, the rsyncs will hang forever (or at least a few days, I haven't let them run any longer than that so I'm nto sure if they'd eventually exit on their own or not). The information on rsync and OS version was sent in my previous email. For now i'm just going to run without -v, as I need to get this going and don't have time to get intimately involved with rsync. But if someone's heard of this before and/or is working on this bug (i assume it's a bug?), and you need mroe info from me, let me know if there's anything I can do. --jessica
Re: rsync takes way too long to perform this....
rsync -avnp remote::gif/ `find /home/www/html/ -maxdepth 1 -name *.[j,g][pg,if]*` /tmp/ If I run this on the local machine, the rsync server, it takes this long: --- root@server (0.34)# time find /home/www/html/ -maxdepth 1 -name *.[j,g][pg,if]* -type f /home/www/html/comparestores_2.jpg /home/www/html/home.jpg /home/www/html/comparestores_3.jpg /home/www/html/specialoffer_apparel.jpg /home/www/html/bike_gary.gif /home/www/html/gary_bike.gif /home/www/html/none.gif real0m0.015s user0m0.000s sys 0m0.000s However if I run it from a client, it will take forever. Too much to run, it seems. Our directory structure has well over a million files. And this is just one directory under /home/www/html. We can't afford the cpu and system load to traverse everything, this is why I am using the find command. Shouldn't this work? It does come back with retrieving the list from the remote server. What OS are you running on both systems?? AFAIK linux with ext2/ext3 has (currently) severe problems with large directories (5000 files). [Work is done to avoid that: see ext2 directory index patch at http://kernelnewbies.org/~phillips/ ] Maybe that's your problem. (In my - and strictly my - opinion, a directory with that many files is unmaintainable. I'd do some partitioning - and if it's only sorting by filetype (.html, .gif, .jpg, ...)) Regards, Phil
Re: rsync takes way too long to perform this....
It is a reiserfs system on the client, and ext2 on the rsync server. The file system is organized lovely. Just a ton of files. On Thu, Nov 15, 2001 at 07:13:09AM +0100, Ph. Marek thus spat: | rsync -avnp remote::gif/ `find /home/www/html/ -maxdepth 1 | -name *.[j,g][pg,if]*` /tmp/ | | If I run this on the local machine, the rsync server, it takes this | long: | | --- root@server (0.34)# time find /home/www/html/ -maxdepth 1 | -name *.[j,g][pg,if]* -type f | /home/www/html/comparestores_2.jpg | /home/www/html/home.jpg | /home/www/html/comparestores_3.jpg | /home/www/html/specialoffer_apparel.jpg | /home/www/html/bike_gary.gif | /home/www/html/gary_bike.gif | /home/www/html/none.gif | | real0m0.015s | user0m0.000s | sys 0m0.000s | | However if I run it from a client, it will take forever. Too much to | run, it seems. Our directory structure has well over a million files. | And this is just one directory under /home/www/html. We can't afford the | cpu and system load to traverse everything, this is why I am using the | find command. Shouldn't this work? It does come back with retrieving the | list from the remote server. | What OS are you running on both systems?? AFAIK linux with ext2/ext3 has | (currently) severe problems with large directories (5000 files). | [Work is done to avoid that: see ext2 directory index patch at | http://kernelnewbies.org/~phillips/ ] | | Maybe that's your problem. | | | (In my - and strictly my - opinion, a directory with that many files is | unmaintainable. I'd do some partitioning - and if it's only sorting by | filetype (.html, .gif, .jpg, ...)) | | | Regards, | | Phil -- Jason G Helfman Network Administrator BizRate.com, Co-Owner 310.754.1264 desk 310.466.2319 cell Fingerprint: DA13 C109 072B CC12 B568 8D84 E9A2 6A7D C479 BCFB GnuPG http://www.gnupg.org Get Private! 1024D/D75E0A36
Re: rsync takes way too long to perform this....
It is a reiserfs system on the client, and ext2 on the rsync server. The file system is organized lovely. Just a ton of files. Well, that's most likely your problem. reiserfs has another scheme of directory operations and no problems with large directories. ext2 unpatched has them. If you're in an experimental mood try using the patches mentioned in http://www.uwsg.iu.edu/hypermail/linux/kernel/0105.1/0896.html That should make your problem vanish. Or, you could use reiserfs too, of course. Regards, Phil
Re: rsync takes way too long to perform this....
It is a reiserfs system on the client, and ext2 on the rsync server. The file system is organized lovely. Just a ton of files. Sorry, the homepage is at http://people.nl.linux.org/~phillips/htree/ Regards, Phil
