Re: More: Re: Synchronizing unison files

The following should work:
    *ignore = Name .unison*

But more accurate would be:
    *ignore = Path .unison*

The difference between these two is that the first form matches the name
".unison" *anywhere* in the dir tree, not just under the root. The second
form matches the entire path under the root. In this case, it will only
match /home/john/.unison and /media/john/ASUS-john/.unison but not, for
example, /home/john/something_else/.unison (whereas the first form would
match this).


On Wed, 14 Feb 2024 at 10:26, John Rose <[email protected]> wrote:

> But when I change my prf file as follows:
>
>
>
>
> *# Unison preferences root = /home/john root = /media/john/ASUS-john
> ignore = Name {Dossier ~/.unison}*
>
> unison still tries to transfer the files inside and gives an error (with
> or without the "*~/")*. Maybe I need a parameter or regular expression to
> ignore the hidden directory?
>
> Thanks and best regards,
>     John
>
> -------- Message transféré --------
> Sujet : Re: [unison-users] Synchronizing unison files
> Date : Wed, 14 Feb 2024 09:32:56 +0100
> De : John Rose <[email protected]> <[email protected]>
> Pour : [email protected]
>
> Thanks for this, Greg,
>
> Previously I was using grsync for backups and unison for syncs, then I
> stopped syncs because moved to a single computer but chose to keep unison
> because of its clear and user-friendly interface, and the facility to
> easily ignore certain elements. The lack of priority to reduce
> inter-version incompatibility of unison is still incomprehensible for me,
> but I have learned to live with it and will now use it to sync two nearly
> identical computers (with big screen for desk us and small for travel). For
> a small-scale application like mine, much better to have only one package
> to worry about. I will exclude ~/.unison as you suggest.
>
> Best regards,
>
>     John
>
> Le 13/02/2024 à 15:19, Greg Troxel a écrit :
>
> John Rose <[email protected]> <[email protected]> writes:
>
> I am synchronizing my Ubuntu home directory to an external SSD and (I
> guess quite naturally) cannot synchronize unison archive files for the
> active directory or the unison log file because they change during
> synchronization. I could ignore the files in the prf (I guess I would
> need a regular expression for the relevant archives files?) but this
> would not change anything. Is there any way around this? else I can
> easily live with it.
>
> I don't synchronize my homedir, or NFS mount it, because different
> machines need different content, are different OS, etc. Instead I have
> shared/foo for various foo and synchronize them (varying destinations).
> So that would work. But here, I am guessing that you are likely
> doing backup rather than "drive the ssd to work and sync it to your
> homedir there", it not being the 90s any more.
>
> unison more or less expects ~/.unison not to be synced. I would suggest
> that you either:
>
> simply exclude ~/.unison
>
> put the contents of ~/.unison someplace outside your homedir and
> symlink it in (not tested, might misbehave because of something I
> don't understand). back it up separately
>
> exclude the log and the ar/fp files that are for this particular sync,
> if they point is to back up including backing up the ar/fp used to
> sync other things to other places
>
> if what you are doing is making backups, use a backup tool instead of
> a sync tool, partly because you want history to recover later from
> undetected loss. Personally I use bup.
>
> --
> ************
>
>                John B. Rose
>                1 Bis rue des Châtre-Sacs
>                92310 Sèvres, France
>
>                Email: [email protected]
>
> --
> ************
>
>                John B. Rose
>                1 Bis rue des Châtre-Sacs
>                92310 Sèvres, France
>
>                Email: [email protected]
>
> --
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
>

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].