similar to: strip setuid/setgid bits on backup (was Re: small security-related rsync extension)

On Fri, 19 Jul 2002, Dan Stromberg wrote: > Many apologies. If we update on the nfs server, as we've intended all > along, we should have no .nfs* files. Well, here's one thing that could make them, even if they're being created only directly, not over NFS. I'm watching the directory you're syncing into. I open the file while it's still there. You delete it, and

I vote for the consistent, complete log format as a solution to this sort of thing, and those who need to take non-rsync related actions based on what rsync did can write their own applications to do so. People keep coming up with some particular thing they need done for their own application, and want rsync to do that too. rsync is a tool to make one thing exactly like another. It is not

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

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

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

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

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,

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

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,

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.

> 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

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

There's a program to apply patches, typically called "patch" Try "man patch". If your system doesn't have, and can't get patch, just read the patches and edit the appropriate files by hand. It's not particularly difficult. Incidentally, I want to point out that there's no good reason to cc rsync-admin@lists.samba.org on a regular post. I've been

rsync -a /opt/config/. DevlServ:/opt/config (see rsync.1) 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

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,