similar to: Password Authentication

Hi All, We have clients which dynamic IPs which we have setup with <host>.dyndns.org addresses. We have added these to the rsync.conf 'hosts allow=" but they are being denied access.. Is there anyway around this? Matt

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

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

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

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

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.

Ah... there's your answer. ssh is working fine, as you say, but you're invoking rsync without telling it to user ssh, so it's using rsh. If you've got this, you don't need rsyncd.conf. The syntax you're using tells rsync to use an external transport. rsync -e ssh file rmt_host:/tmp Tim Conway tim.conway@philips.com 303.682.4917 Philips Semiconductor - Longmont TC 1880

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

- 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

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

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.

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

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

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

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,

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

I'm not sure what the problem is. Here's a snip of my log (very similar setup, but from server to remotes): 2001/05/17 14:26:59 [29226] rsync on ToolSyncModules/ToolSyncModuleList from irvnetsvr (134.27.9.31) 2001/05/17 14:27:00 [29226] wrote 23292 bytes read 128 bytes total size 23179 2001/05/17 14:27:01 [29227] rsync on ToolSyncModules/ToolSyncMastersList from irvnetsvr

I have written an application in perl, to run multiple rsyncs, retrying those which fail. I have started getting this error on very large modules since i moved to the latest CVS version. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ToolSyncProgress Succeeded Getting big/tools/vlsi_local/etc from willy at 1004767211:2001:11:3:6:0:11. ToolSyncProgress Getting big1/cadappl1/hpux

rsh gives a reduced environment. if rsync on ApplServ isn't in /bin or /usr/bin, that's probably your problem. It's such a common problem that somebody added the "--rsync-path=" option for just such needs. In my case, i have rsync in /cadappl/encap/bin (symlinked into /cadappl/encap/packages/rsync.something/bin). It's in my path, but not the base system path given