Anne Wilson wrote: Use rsync for such tasks. It natively understands how to move files over ssh. Eg rsync -avz mysourcedir user@desthost:/path/on/destination will just update/transmit files changed in the source dir compared to the destination. -Andy

On Sat, Mar 18, 2006 at 04:05:20PM +0000, Anne Wilson wrote: it only does that with the --delete option, not by default. -- In the 70's we wore flares because we didn't know any better. What possible excuse does the current generation have?

Anne Wilson wrote: Here's a sample of what I use every day to sync my home directory to another machine where ssh runs on port 8090, excluding the Cache of any mozilla based browser (--exclude=Cache) , deleting any excluded files that by accident may have been sent to the destination and files that have been removed (--delete-excluded includes --delete) and copying the contents of symlinks, instead of copying the links (--copy-links). rsync -avz -e 'ssh -p 8090' /home/pmacedo/ my_other_machine:~/sync/ --delete-excluded --exclude=Cache --copy-links One caveat: you must be running rsync either from the source or the destination machine, since rsync wont do remote to remote syncs using ssh. That's usually what I use and I've never needed any other options besides those to do any type of sync. -- Pedro Macedo

On Sat, 2006-03-18 at 18:01 +0000, Anne Wilson wrote: try: rsync -e "/usr/bin/ssh" --exclude=.* -auvz /home/anne/ ann@borg:/home/anne/ >~/Desktop/rsynctest.txt

Try to use the -e flag : rsync -auvz -e ssh from where -- Luc MAIGNAN /*WinXpert*/ Directeur technique Tél : +33-1 69 51 39 50 e-mail : luc.maignan(a)winxpert.com Andy Green a écrit :

On Saturday 18 March 2006 19:20, Luc MAIGNAN wrote: I've hit a brick wall there, Luc. I set up keychain to monitor both ssh-keys and gpg-keys, but I keep getting messages that one of my gpg keys is not found. When I tried a command with the -e flag as you suggested it immediately failed with "/home/anne/.keychainrc: line 1: 2F62DB48: command not found". I had put this problem aside for the moment, thinking that the gpg-key was not important in this situation, but it looks as though I was wrong. It looks as though I may have to address this problem first. Anne

On Saturday 18 March 2006 21:42, Les Mikesell wrote: I can do 'ssh anne@borg' and connect to the remote box - no problem, and the key is passed. What I'm trying to do is find the commands I will need so that I can put together a script to do regular copies across the lan. I'll struggle on with the docs - it's no worse than the first time I got gpg-agent going ;-) Anne

On Sat, 2006-03-18 at 18:01 +0000, Anne Wilson wrote: The .* includes all hidden (.xxxx) files, the .. (parent) directory, and the . (current) directory. It may not have been what you wanted.

Anne Wilson wrote: Jeff Vian told her: Anne replied: I should have thought --exclude .[a-z]* or --exclude .??* would have got rid of most hidden files and directories. A quick check on my home directory suggests both would do the job [1] I'd also suspect that for the test, you need to --exclude ~/Desktop : things could get odd if you repeatedly try to syncronise all of your home directory to somewhere underneath it. Hope this helps, James. [1] Assuming that you haven't changed LANG or LC_COLLATE to C, in which case .[a-z]* won't get .DCOP*. -- E-mail address: james | [Bradford Cathedral] took 194 years to complete. A @westexe.demon.co.uk | construction period of nearly two centuries may seem | ridiculous to us, but of course builders were a lot | quicker in those days. -- "ISIHAC", BBC Radio 4

On Tuesday 21 March 2006 07:28, James Wilkinson wrote: For the test I dropped the '-r', but forgot to exclude ~/Desktop, though it wasn't important at this point because it was being re-directed to another directory. Here is what I gave: rsync -e "/usr/bin/ssh" --exclude=.[a-z]* -auvz /home/anne/ anne@borg:/home/anne/Test yet it started to act recursively. Most of the hidden files were excluded by the filter, but it let .DOCPSERVER_box.domain.lan, .ICEauthority and .Xauthority. I don't think that the first one is a problem, since it is linked to the box, but the other ones probably are. What do you think? I haven't spotted the relevant bit in the man page, so do you list the two excludes simply space-separated? Anne

I wrote: Anne Wilson replied to it, dropping the footnote: Jeff Vian wrote: Actually, I should have said .[a-Z]* . But that's why I added the footnote. File globbing (at least in bash) observes the LC_COLLATE environment variable, or LANG if LC_COLLATE is not set. And that dictates how letters sort. The "C" locale observes traditional case sensitivity, the way you suggest. But en_GB.UTF-8 (which I imagine both Anne and I are using), en_GB, en_US, fr_FR, and (I imagine) most other locales sort "aAbBcCdD...", with other accented characters in there, too. So [a-Z]* gets the lot. That's also why ls no longer lists the filenames beginning with capital letters before the rest. Hope this helps, James. -- E-mail address: james | The winds, however, get very lazy that time of year; @westexe.demon.co.uk | they don't bother going around you, they just go | right on through. | -- Joe Zeff

Anne Wilson wrote: Not usually, no. But it sounds as though you've got problems with part of your computing environment using UTF8 and part of it using ISO 8859 variants. UTF8 is undoubtedly superior, but the transition period is a bit sticky... Can you open a shell and type echo $LANG It should return en_GB.UTF-8 which should confirm your settings. And you'd probably better check /etc/sysconfig/i18n, too. With this set up, you should be good to enter and save accented letters. You should also be able to receive (properly formatted) e-mails with accents in, since the e-mails should contain headers describing the encoding used. So, for example, уоυ ѕhουld ье аьlе to read that (with any luck, and a good font) even though it contains quite a few Greek and Cyrillic letters, because this message will have a header saying that it's encoded in UTF8. The problem comes when you have text files that come from non-UTF8 systems, or filenames from non-UTF8 systems, or applications which don't understand UTF8. If you're seeing double spaces, then you're probably seeing UTF8 data displayed in a non-UTF8 program (or system). In which case, it would be helpful to know precisely which program or system that is, so we can recommend better settings. Hope this helps, James. -- E-mail address: james | Banana in disk drive error @westexe.demon.co.uk |

I asked Anne Wilson: She replied: Change that value in /etc/sysconfig/i18n. Although the difference is simply that you'll occasionally get American content / spelling / preferences. You shouldn't have problems with accents or unusual characters due to the difference. (Having said that, I'm still on FC4. Check /usr/lib/locale and make sure there's an en_GB.utf8 directory there if you're on FC5). So from where did you get those files? Were they generated on another computer? What happens if you ls them from the command line? As for the single e-mail -- I'd blame the other end, personally. Hope this helps, James. -- E-mail address: james | actor: (n) a piece of scenery that has the audacity @westexe.demon.co.uk | to move once lit.

Anne Wilson wrote: Odd. I don't have one on this system, and I haven't noticed any problems... A backup from an FC3 machine listed SUPPORTED="en_GB.UTF-8:en_GB:en:en_US.UTF-8:en_US:en" although I doubt both en references are strictly necessary. I can't find any references as to where it is used... I asked (about files that were apparently incorrectly named) Anne replied: That's actually a different symptom of the same problem. UTF8 takes two bytes to store most common non-ASCII characters, whereas the ISO-8859 family always uses one byte. What you first described was seeing the two UTF8 bytes in an ISO-8859 program, so each accented character shows as two ISO-8859 characters (some of which will probably be "illegal", so you'll see spaces or something similar there). What you've just illustrated is an ISO-8859 name viewed in an UTF-8 environment, where two ISO-8859 characters are interpreted as one illegal UTF-8 character. My first reaction is to blame the generating program (what was it?) In my experience, many MP3 programs, following Winamp's example, have gone flat-out for skins and custome text-handling. Too many of them don't support UTF8 in $LANG properly. Alternatively, what did the server box use to run? How did you transfer the files? Red Hat went to UTF-8 early, and many other distros took a lot longer to upgrade. And transferring files might not get the conversion right. (You used to use Mandriva, didn't you? I'm not sure when they adopted UTF-8...) I wrote: Anne said: Um. Mail clients have no business not knowing which encoding they're using. And if they know that, they've no business not putting it into the headers of outgoing e-mail properly. We've proved that your e-mail client can receive UTF-8. I suppose there's still the chance that your correspondent used a weird encoding that your client didn't understand. But you're not going to get the "right" message anyway in those situations, except by blind luck. James. -- E-mail address: james | In the Royal Air Force a landing's OK, @westexe.demon.co.uk | If the pilot gets out and can still walk away. | But in the Fleet Air Arm the outlook is grim, | If your landings are duff and you've not learnt to | swim.

On Wednesday 22 March 2006 02:42, Jeff Vian wrote: Yes, I suspected that would be the solution, but held off until I resolve the multiple exclusion question and recursivity. I will make local backups to RW of any config files I suspect I'd want to keep. However, can you see any reason why the command I gave would act recursively? That was totally unexpected, and undesired at this stage. I need to workout the exclusion list first. What about multiple exclusions, Jeff? Do they get listed space-separated? Or is there some way to pass a file as the parameter? Anne

On Wednesday 22 March 2006 16:49, Les Mikesell wrote: Ah yes - I had read it, but missed the fact that -r is included. Yes, finally. I just hadn't intended it at that stage. It's a matter of trying to make sure that I understand all the implications ;-) That only leaves the question of how to set multiple exclusions. It looks to me as though exclude-from=filename is going to be the best way to do it. Is that right? With a man page this long you can read until you are bog-eyed ;-) Anne

On Thu, 07 Feb 2008 14:56:45 -0800 Gerhard Magnus <magnus(a)agora.rdrop.com&gt; wrote: I thought it was a bug when I first saw it: https://bugzilla.redhat.com/show_bug.cgi?id=389411 I don't see any comments on the bug since it was entered, so I have no clues to offer.

On Saturday 18 March 2006 12:09, Anne Wilson wrote: So print it & take it to the middle of the house, where you can read while attending to other bodily needs. Around my place its also called the reading room. :) -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

Anne Wilson wrote: Clearly, you have not learned to read the documentation.

On Saturday 18 March 2006 15:27, Andy Green wrote: Oops - I think I've just made a terrible mistake. I rsync'd my home directory, forgetting that it would take the hidden files and config files with it. Now I'll have to see what damage is done. Anne

On Saturday 18 March 2006 17:36, Pedro Fernandes Macedo wrote: That sounds very useful indeed ;-) Thanks Anne

On Saturday 18 March 2006 15:51, Gene Heskett wrote: I do a lot of photo-processing and video-processing, which takes up a lot of disk space, so I've put a large drive on the remote box and want to collect everything together there. Wouldn't rsync delete files on the remote box when I remove them here to make space? Anne

Anne Wilson wrote: Another option is to use sitecopy, I use it to maintain my web sites (which I keep a local copy of). I think you'll run into the same problems as you are seeing now so it may not work any better. http://www.lyra.org/sitecopy/ -- Linux Home Automation Neil Cherry ncherry(a)linuxha.com http://www.linuxha.com/ Main site http://linuxha.blogspot.com/ My HA Blog http://home.comcast.net/~ncherry/ Backup site