similar to: Sorry about that-New way to run Rsync on OSX

If it's anything like the rooms I saw last year...some rooms have "wardrobes" meaning that you have a unit with a shelf, a "closet" cabinet type thing, and about 5 drawers. If you have lots of clothes, bring extra storage containers because thos drawers can't really hold much. Or don't bring so many clothes:) I think some of the two room doubles have huge-ass floor

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

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

Hi!:) - try using the sudo command as a prefix to all of that. I know that if I didn't do that it would default to nobody.nobody when I copied. -Tito > > Hi All, > I recently installed Rsync to perform backup features - this > includes backing up a /home dir and keeping ownerships/permissions > intact is obviously very important.... > > However when I perform.

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

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

First, an item to fix: the substitution of "-P" for "-p". All good operating systems are case-sensitive, and many utilities, ssh included, are case sensitive about their options. "-P" is passed along with the "-p" to signal that the next parameter is the passphrase, to enable passphrase setting directly in the commandline. If that's wrong,

Approximated petitioner: Perhaps this will help. SunOS 5.7 Last change: 25 Jan 2002 5 User Commands rsync(1) -C, --cvs-exclude auto ignore files in the same way CVS does --existing only update files that already exist --ignore-existing ignore files that already exist

A: do you have a "hosts allow" or "hosts deny" in rsyncd.conf? B: what version are you using? It seems i've seen messages about rsyncd in some versions refusing to allow unresolvable names in. C: Are you able to access the rsyncd, and just wonder about the log entries, or are you unable to get in? If it's just a log complaint, I wouldn't worry about it. Most

I just did a win2k install, and as I thought i'd remembered, it asked whether the hardware clock was UTC or localtime (and recommends localtime). Of course, I chose UTC, but most would probably follow MegaSloth's recommendation. I don't know how to change it on an already-installed system, though. Does anyone else? Tim Conway tim.conway@philips.com 303.682.4917 Philips

Unless told otherwise, rsync uses rsh to contact the remote system.=20 Another popular option is ssh. Both of these protocols use the logged-in=20 username, unless specified otherwise. What rsync really does is "rsh=20 remotehost rsync --server-and-other-undocumented-options". If you can't=20 "rsh server rsync --version", rsync won't work with rsh. Same with ssh. I

You're obviously not the first to need this. That's why the '--bwlimit=' option was added. Set it to however many Kbps you want rsync to use. I usually use 768 going over our wan, to spare some bandwidth on the T1, and maybe 10000 over the lan (in my case, all the dasd is nfs). I suspect that it may affect local-to-local transfers as well, but haven't tested it, but

I wouldn't worry about users reading each others files, either, if you give each his own module, password-protected. 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,

Oh. Now i feel like an *enlightened* idiot. I 've always thought of a checksum, crc, or whatever as giving 1/2^^length certainty, and I have a sense that that knowing the file length adds another amount of certainty, though I can't quantify that. I just know that if the size doesn't match, the checksum doesn't matter. I'd never considered the implications of the

not logging into it, either by hitting escape at the login prompt, or=20 configuring it to not ask, thus, it has no idea what username you are. Am = I right? 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,=20

I have a similar problem with rsync, though it's not consistent. sometimes, things just don't come over, and sometimes, things just don't get deleted. Repeated runs usually correct it. If it's the case of a directory being replaced with a non-directory, you'll have to add "--force" to get it to happen. Hope it helps. Tim Conway tim.conway@philips.com

Tim, I reported a protocol data stream error on 9/8/2002 Deatils are in my postes at that time rsync still fails everytime I run it. This time I added three v's as you just suggested and rsync just hung with two tasks in execution thus: root 3178 0.1 0.9 1796 868 pts/1 S 09:57 0:00 /usr/bin/rsync -vvva --delete --exclude=root/snapsh root 3179 0.0 0.6 1628 632 pts/1

Actually, what I do also propogates deletions. Since someone may unpack a tar containing files with earlier mtimes than a marker file, a simple --newer won't do it for us, either. Instead, I generate a list of all items, consisting of name and type, to which i append number of links, size, and mtime for files; link destination for symlinks; and for directories, fifos, chars, blocks,

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:

Wayne: If anybody can make that work, I'd bet you could. The basic rsync algorythm is in place, so as you say, it would mostly be a matter of list generation. You'd have to hold on to any files with <1 link, in a seperate list, to find all the linkage relationships, which could grow a bit, but it does sound more efficient. Maybe a third pipe to send the files over as you go?