Re: Unison on 4 Computers?

Benjamin, et al --

...and then Benjamin C. Pierce said...
% 
% > which one syncs with one of the other, or in a round robin, or ...
% 
% I've found using a star topology the simplest to understand.

Yeah; I would figure so, too.

% 
% > The only thing of which to beware is that you have only one unison
...
% 
% As long as the roots are associated with different archive files, there

Hmmm...  What again is an archive file?  Is that the archive checksum
file that is made with a given profile?

% should be no problem with running any number of unison processes in

Cool!

% parallel.  The only thing you really don't want is two unison processes
% trying to manipulate the same archive.

So something like

  root /home/backups/jpo/davidtg
  root jpo:/home/davidtg

RE: Unison on 4 Computers?

what about the      #*.unison.tmp     files ?
don't they get erased  when a new session starts ?

(merun  Win2K  3way)

S

> -----Original Message-----
> From: Benjamin C. Pierce [mailto:bcpierce <at> cis.upenn.edu]
> Sent: Tuesday, September 30, 2003 18:00
> To: David T-G
> Cc: Unison Users' List; stormyforty
> Subject: Re: [unison-users] Unison on 4 Computers?
> 
> 
> > Well, unison can be made to talk one at a time to as many 
> other machines
> > as you want (or even to talk to itself on the same 
> machine).  You could
> > run your sync from one computer to each of three, or in two pairs of
> > which one syncs with one of the other, or in a round robin, or ...
> 
> I've found using a star topology the simplest to understand.
> 
> > The only thing of which to beware is that you have only one unison
> > process running at a time on a machine.  As I understand 
> it, you can't
> > even synchronize local root A with remote root A while 
> syncing local root
> > B with remote root B, no matter on what machine remote B lives.

Re: Unison on 4 Computers?

On Tue, Sep 30, 2003 at 05:59:34PM -0400, Benjamin C. Pierce wrote:
> > Well, unison can be made to talk one at a time to as many other machines
> > as you want (or even to talk to itself on the same machine).  You could
> > run your sync from one computer to each of three, or in two pairs of
> > which one syncs with one of the other, or in a round robin, or ...
> 
> I've found using a star topology the simplest to understand.
> 
> > The only thing of which to beware is that you have only one unison
> > process running at a time on a machine.  As I understand it, you can't
> > even synchronize local root A with remote root A while syncing local root
> > B with remote root B, no matter on what machine remote B lives.
> 
> As long as the roots are associated with different archive files, there
> should be no problem with running any number of unison processes in
> parallel.  The only thing you really don't want is two unison processes
> trying to manipulate the same archive.
> 
>      - B

IIRC this does apply to "beta" versions only - the latest stable
(2.9.1) does remove temporary files and folders created by a 2nd
running instance?

louis
--

-- 
Jürgen "Louis" Fluk                         mailto:j.fluk <at> ntm-gmbh.de
New Technologies Management GmbH            Tel +49 89 993415-56
Stefan-George-Ring 24, D-81929 München      Fax +49 89 993415-99

Re: Unison on 4 Computers?

> IIRC this does apply to "beta" versions only - the latest stable
> (2.9.1) does remove temporary files and folders created by a 2nd
> running instance?

Sorry, I'd forgotten about this.  Version 2.9.1 will remove temp files of
other running unison processes during update detection.  2.9.20 and later
versions will remove only temp files associated with the current set of
roots.

    - Benjamin

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Upgrade to 128-Bit SSL Security!
http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/26EolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
unison-users-unsubscribe <at> onelist.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 

Re: Unison on 4 Computers?

Benjamin, et al --

...and then Benjamin C. Pierce said...
% 
% > IIRC this does apply to "beta" versions only - the latest stable
% > (2.9.1) does remove temporary files and folders created by a 2nd
% > running instance?
% 
% Sorry, I'd forgotten about this.  Version 2.9.1 will remove temp files of

Ahhh...

% other running unison processes during update detection.  2.9.20 and later
% versions will remove only temp files associated with the current set of
% roots.

Good to know.  Thanks, Jürgen!

% 
%     - Benjamin

Thanks & HAND

:-D
--

-- 
David T-G                      * There is too much animal courage in 
(play) davidtg <at> justpickone.org * society and not sufficient moral courage.
(work) davidtgwork <at> justpickone.org  -- Mary Baker Eddy, "Science and Health"
http://justpickone.org/davidtg/      Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

Received unexpected header from the server

Hi,

I'm using:
- A Unison 2.9.1 client in a Windows XP platform,
- A Unison 2.9.1 server in a Solaris platform.

The connection from the client to the server is
performed through RSH coming from Cygwin 1.5.5-1 .

As I run the client, I get the following error
message:

<<
[remote] Shell connection: rsh (rsh, republique,
/nfs/home/xloiseau/bin/unison.solaris-textui, -server)

Received unexpected header from the server: expected
"Unison 2.9.1\n" but received "Unison 2.9.1\013".

This is probably because you have different versions
of Unison installed on the client and server machines.
>>

A lot of messages can be found through Google about
such problems which occured in the past with Cygwin
1.3.11 .

Among the found proposed solutions, I have tried to
set the CYGWIN environment variable to "binmode" or
"nobinmode".

File Synchronizer

Re: Unison - can I get all the confirmations to appear in one go.

Hi Andrew,
	You can use unison in batch mode (unison -batch) but have a read of  
the manual about other cool stuff you can do with .prf files.

John

On Wednesday, Oct 1, 2003, at 01:54 Australia/Brisbane, Andrew Black  
((li)) wrote:

> Hi
> Is there any way of getting unison to list all the changes in one go,  
> and
> then ask for conirmation.
> I.e., I would like to see all the messages of the form
>
> changed  ---->            xxxx.txt
> changed  ---->            yyyy.txt
> changed  ---->            zzzz.txt
>
> to appear without promping, then a single confirmation :
>
> Proceed with propagating updates? []
>
>
>
> ------------------------ Yahoo! Groups Sponsor  
> ---------------------~-->
> Upgrade to 128-Bit SSL Security!
> http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/26EolB/TM
> --------------------------------------------------------------------- 
> ~->
>
> To unsubscribe from this group, send an email to:
> unison-users-unsubscribe <at> onelist.com
>
>
>
> Your use of Yahoo! Groups is subject to  
> http://docs.yahoo.com/info/terms/
>
>
>
>

Regards,
	John B. Hewitt
	Mobile: 0408 22 09 13
	www: www.stcpl.com.au

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Upgrade to 128-Bit SSL Security!
http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/26EolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
unison-users-unsubscribe <at> onelist.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 

internal error syncing red hat 8 and 9

I've run into an odd problem: I've just upgraded my laptop from Red Hat
8.0 to Red Hat 9, while my desktop machine remains on Red Hat 8.0 for
the time being. Since doing the upgrade I've had unison fail to
synchronise using configurations that were working fine prior to the
upgrade. Unison scans the directories on both machines before reporting
"Internal error: New archives are not identical", but the contents of
the .unison directory have not been corrupted during the upgrade.

During the upgrade, however, I did backup and restore all the files on
the filesystems, so each file's inode number is likely to have changed.
Is this likely to be causing the problem? Any ideas how I could
workaround the problem? Does it represent a bug in unison?

-Mark.

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Upgrade to 128-Bit SSL Security!
http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/26EolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
unison-users-unsubscribe <at> onelist.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 

Re: internal error syncing red hat 8 and 9

> I've run into an odd problem: I've just upgraded my laptop from Red Hat
> 8.0 to Red Hat 9, while my desktop machine remains on Red Hat 8.0 for
> the time being. Since doing the upgrade I've had unison fail to
> synchronise using configurations that were working fine prior to the
> upgrade. Unison scans the directories on both machines before reporting
> "Internal error: New archives are not identical", but the contents of
> the .unison directory have not been corrupted during the upgrade.
> 
> During the upgrade, however, I did backup and restore all the files on
> the filesystems, so each file's inode number is likely to have changed.
> Is this likely to be causing the problem? Any ideas how I could
> workaround the problem? Does it represent a bug in unison?

I'm not precisely sure what is causing the behavior you're seeing, but in
general changing inode numbers out from under Unison is not a good idea --
it does rely on their stability.

The workaround for this (and for other situations where Unison seems
confused) is to delete all of Unison's archive files and synchronize again;
if the two replicas are content-identical, Unison will realize this and
recreate its archives.  (If they are not identical, you may have a little
cleanup to do -- e.g., if it sees a file on one side and not the other, it
will always try to propagate it -- so you will want to run it in interactive
mode and have a look at what files it thinks it wants to transfer.)

    - B

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Upgrade to 128-Bit SSL Security!
http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/26EolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
unison-users-unsubscribe <at> onelist.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/