similar to: rsync-2.5.5 hangs in client-server mode

The way gnutar "preserves" atime is by noting it before the read, and setting it back after the read, thus wiping out a legitimate setting of atime occuring during that interval. Yeah, the netapps mess with unix times. Did you notice that mtime and ctime always match? Now that I know you're on a netapp, though, your problems are solved. Snapshot and sync from the snapshot, then

Tarun: I don't use rsync to windows - just too much trouble and no need, but, I think the problem is the embedded colon in the path. Administrator@USB-FLATUS ~ $ touch abc:def Administrator@USB-FLATUS ~ $ ls -l abc* -rw-r--r-- 1 Administ None 0 Aug 27 12:34 abc Administrator@USB-FLATUS ~ $ rm abc:def Administrator@USB-FLATUS ~ $ tar -tvf /n/a.tar -rw-r--r-- tconway/Vlsieng 29

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

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

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

Since I get so many direct inquiries, I feel obligated to mention that I just got laid off, so am losing this address. Bye. Tim Conway conway.tim@spilihp.com reorder name and reverse domain 303.682.4917 office, 303.921.0301 cell Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, caesupport2 on AIM

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,

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

Subject: rsync client-server users Are you using rsync in a client-server configuration? If you are, and if you have set up your cron or anacron tables to run an rsync client, does the client ever just hang? I am running one rsync server and two rsync clients, both clients are under control of anacron. And they both hang on the rsync command, forever. All three systems run Red Hat 7.1 and

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

Your users have rsh access to the machine, and are getting wherever they want, using the server:/path syntax. if they were using the server::module syntax, they would be restricted to only what's provided by the modules. If you don't want them getting everything all over the system, you will need to prevent shell access. Tim Conway conway.tim@sphlihp.com reorder name and reverse

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

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

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

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:

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

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.