similar to: AW: ssh + permissions

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

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....

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

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

Sonu: I'm giving the whole history to the rsync list. If the tests i subscribed passed, yet you get that error, it's more in depth than i can go into. You've got 1 hour, let's hope somebody immediately recognizes the problem. I've got some ideas, but no time to explore any more for you. Gentlemen: does anybody see a quick resolution for Sonu? Looks like he's

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,

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

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

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

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,

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

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.

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?

> If you have a set of files that are "common" to each side but for whatever reason the content of which you want to keep separate and "localized" then look into using --include and --exclude rules or perhaps an exclusion file. The syntax always gets me > and it might take a couple of tries to get the right sequence of element inclusions. Rene > --__--__-- >

- call me ignorant... but I am not above asking. Where do I define $RSYNC_SSH=ssh at? Thanks for the info!! David -----Original Message----- From: rsync-admin@lists.samba.org [mailto:rsync-admin@lists.samba.org]On Behalf Of tim.conway@philips.com Sent: Tuesday, January 15, 2002 7:08 PM To: David L Nickel Cc: rsync@lists.samba.org Subject: Re: SSH Error Ok, you're talking about ssh, and