similar to: secrets file, reverse resolution problems

Hello All, A good day to you all. Is there any way to prevent the rsyncd daemon f rom performing the forward/reverse lookups for rsync clients? Thanks in advance. __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.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.

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

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. My goal is to use rsync to syncronize box1 and box2. On box2, I have a tapedrive which I write the data I syncronize from box1 every night. On box1, my /etc/rsyncd.conf looks like this: root@box1# cat /etc/rsyncd.conf max connections = 1 syslog facility = local6 [tmp] path = /tmp read only = yes comment = export of /tmp hosts allow = box2 auth users

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,

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,

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

Whoops, I apologize for the off topic e-nail. I meant to write a reply but I mixed up my messages to the various listservers I'm subscribed to. I'll remember to check my address next time. I've found a new way to run Rsync, it works pretty well, and involves a disk image mounted on a server that's created with Disk Copy. It serves our purpose pretty well for what we're doing

Hi, a few months ago I posted a message about using LDAP to store rsync secrets in LDAP. I received a response about patching the rsync source code with a patch file. I am now finally getting around to doing this, and when I tried to use the patch command 'patch --verbose ./rsync-2.5.6/authenticate.c rsync-ldap.patch' , it gives me the following error: Hmm... Looks like a unified diff

Hello, after looking through the archives, I've not found any previous answers that covered my situation. Last week, I lost the ability to rsync from a solaris 2.8 box to a windows 2000 box that had worked fine for months previous to the failure. I looked through the rsyncd.log file and found "transfer interrupted (code 20) at rsync.c(229)" entries starting on the date which the

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

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. As the man page explains, and this message http://www.mail-archive.com/rsync@lists.samba.org/msg04069.html summarizes from the different man pages rsync will not use the password file if it is world readable. Now, if the rsync team was so kind to add the "strict mode" option for the cygwin platform to ignore if the file is world readable when running in daemon mode why

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:

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1918950298-1868141776-898362261=:6767 Content-Type: TEXT/PLAIN; charset=US-ASCII Something to think about for CRAN's future. best, -tony --1918950298-1868141776-898362261=:6767

Hullo, all. I diligently consulted the suggested reading on the way in: > Welcome to the rsync@lists.samba.org mailing list! PLEASE READ THIS > IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: > http://www.tuxedo.org/~esr/faqs/smart-questions.html 'Twas a quick read, given that I'm the co-author. ;-> I recently received an odd inquiry from someone I didn't know at all,

I got Large files working fine on Solaris, just make a 64bit binary :). Seriously, I would try making a 64bit binary for HPUX as well(something like +DA2.0W for 64bit PA_RISC). Robert Weber University of Colorado -------- > > I am currently writing disaster recovery software for the company I work > for. I have been watching rsync development now for the past couple of

Skipped content of type multipart/signed-------------- next part -------------- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

When rsyncing over ssh my retrieval will pooch out when there's an iso image introduced. I'm not terribly interested in monitoring files and don't care much if I do download these. Is there something I'm missing to allow files of this size to transfer??? Steve Mallett