similar to: rsync HELP!!!

Tarun: I don't use rsync to windows - just too much trouble and no need, but, I think the problem is the embedded colon in the path. Administrator@USB-FLATUS ~ $ touch abc:def Administrator@USB-FLATUS ~ $ ls -l abc* -rw-r--r-- 1 Administ None 0 Aug 27 12:34 abc Administrator@USB-FLATUS ~ $ rm abc:def Administrator@USB-FLATUS ~ $ tar -tvf /n/a.tar -rw-r--r-- tconway/Vlsieng 29

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ /users/tconway>man rsync |grep environment Reformatting page. Wait... done environment variable. the environment variable RSYNC_PROXY to a hostname:port pair environment variable RSYNC_PASSWORD to the password you want WARNING: On some systems environment variables are visible RSYNC_RSH

Hi, I am trying to mirror a server every night using rsync. I have to backup multiple directories and multiple individual files. I also want to use ssh as transport. The problem is that I cannot get ssh to work without asking password for each step. I tried the public key thing but it doesnt work. Can some one give instructions for a layman like me. Also I want to know how to pass argument to

see a copy of your rsyncd.conf? 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....

The "-a" option (the "--links", "--perms", "--devices", and "--times" options are redundant, as they, as well as "--owner", "--group", and "--recursive" are implied by "-a" )does dictate that permissions on files being sent be brought over from the source. Are all files losing permissions, or only files

I keep getting these smarmy sermons from somebody's mail account. I include my response to it below, though from its message, it probably won't be read. 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,

I should have specified what i was replying to. This section seemed to be in reference to what I had experienced before. " > Well, I'm stumped too. (Although I thought I'd read that the > default timeout was not infinite when not otherwise specified, > but I've got so much going on right now that I could easily be > confused on that one!) > " Tim Conway

You're set, unless you declined ssh in your cygwin installation (without cygwin, you're not doing rsync from windoze). It's just like unix, in that case. (Bonus clue: Under related commands for ssh, you'll find ssh-keygen). If you don't actually need to secure your content (you're not naked on the internet, for instance), you can just let rsync use plain old rsh

Gouri: close. Try "Ssh-keygen -p -P ''". You might argue that ssh should guess that -P imlplies -p, but that's an issue for your ssh maintainer. Also: you don't ordinarily distribute the private key. You need the PUBLIC key in $HOME/.ssh/authorized_keys on any system you want to access with the private key. Maybe i'm seing your application backward, and you

The way gnutar "preserves" atime is by noting it before the read, and setting it back after the read, thus wiping out a legitimate setting of atime occuring during that interval. Yeah, the netapps mess with unix times. Did you notice that mtime and ctime always match? Now that I know you're on a netapp, though, your problems are solved. Snapshot and sync from the snapshot, then

Wang: I take it you mean that your mail bounced. Your domain is probably in the RBL or something. The commandline you give is an attempt to contact a rsyncd server. That means that the server you're contacting would have /etc/rsyncd.conf, and either an appropriate entry in /etc/services and /etc/inetd.conf, or would be started manually with "rsync --daemon". I'm guessing

In order to do rsync over ssh without providing a password, you must be able to ssh without a password. The --password-file= option is to provide a password for a rsyncd server (run as rsync --daemon) password. rsync cannot provide a password to an external transport like ssh or rsh. You will find that if you do "ssh -l wl 192.1.4.231 uname -a", for instance, it will ask for a

Well, Robert, at least you're to a consistent state from which maybe the more capable people on this list may be able to help you. I'm ccing the list, as I don't see anything I can help with. You might try it again with -vvv on the client side, to generate more detail. As it looks like it's dying in connection setup, the output shouldn't be cluttered with a mass of

rsync has already explained it to you, in the error message. both the list of usernames and passwords for everybody, and your file containing the password you want to use, are world-readable. The rsync.secrets file should be readable only by root, and the .rsyncpw file should be readable only by simpson. This is all well documented:

the --pasword-file= option is only for passing a password to a rsync server, as you have set up with the rsync --daemon process. Your rsyncd.conf file is fine, too. The problem is that you aren't calling your rsync daemon from your commandline. You are trying to connect via rsync to host as axlink and start a 'rsync --sender' process, to transfer data within the ssh process.

I see very odd results from rsync 2.4.7pre1, the latest cvs version (sept 12, i think was the last modified file). We have a number of network-attached storage devices. 10/100 ethernet, nfs2 mounted (under nfs3, they buffer deletes, and recursive deletions fail). Usually, these are kept syncronized across a wan by a nightly cronjob, We have a few we keep in reserve, which we syncronize

Salim: I suspect that if you check the timestamp, you'll find that that binding failure is left over from an earlier attempt, before you were properly configured. Your description of you inetd.conf/services setup sounds correct. Your commandline, though, shouldn't work. You name a directory as the source, but don't say to do its contents. However, I would expect an error from

This is my first post so first of all I will say hello to everyone. I have rsync configured and working properly on my local network however when I try to connect from a remote host (one located in a different state) the connection times out. I was wondering if there was another way to set the timeout besides in the rsyncd.conf file? As I said the connection works fine on the internal lan, but

Your users have rsh access to the machine, and are getting wherever they want, using the server:/path syntax. if they were using the server::module syntax, they would be restricted to only what's provided by the modules. If you don't want them getting everything all over the system, you will need to prevent shell access. Tim Conway conway.tim@sphlihp.com reorder name and reverse

it's in syscall.c, not generator.c You'll have to save the status of the lstat, modify the mode in st, and return the lstat status. I don't know how to do it, though. #if SUPPORT_LINKS int do_lstat(const char *fname, STRUCT_STAT *st) { #if HAVE_OFF64_T return lstat64(fname, st); #else return lstat(fname, st); #endif } #endif Tim Conway tim.conway@philips.com