Unison and mac osx

Dear all,

I have experienced difficulties with synchronizing a directory between a linux and a mac osx OS. This
directory contains filename with non-ascii characters. I read that unison compare filenames with a
low-level representation and that accented characters are not represented the same way on both OS.

Do you know if there is a solution, or can you confirm that there is no solution for synchronising between
this two OS ?

Best regards
SL

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/unison-users/join
    (Yahoo! ID required)

<*> To change settings via email:
    unison-users-digest <at> yahoogroups.com 
    unison-users-fullfeatured <at> yahoogroups.com

Setting "nice" level for server?

Hello,

Is it possible for the client to execute the server process with a
given "nice" level?

I see that it's possible to specify the path to the unison binary so
perhaps this could be used to execute a wrapper that sets "nice",
but I wondered if there was a more elegant way.

Cheers,
Andy

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/unison-users/join
    (Yahoo! ID required)

<*> To change settings via email:
    unison-users-digest <at> yahoogroups.com 
    unison-users-fullfeatured <at> yahoogroups.com

Re: Setting "nice" level for server?

> Is it possible for the client to execute the server process with a
> given "nice" level?
> 
> I see that it's possible to specify the path to the unison binary so
> perhaps this could be used to execute a wrapper that sets "nice",
> but I wondered if there was a more elegant way.

I think that's the way to do it.

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/unison-users/join
    (Yahoo! ID required)

<*> To change settings via email:
    unison-users-digest@... 
    unison-users-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    unison-users-unsubscribe@...

Unicode support status?

Re: Unicode support status?

I'm not sure how many people are using the unicode support actively,  
but in other respects the developer version seems very stable.   
Anybody have any opinions on how well unicode is working now?

     - Benjamin

On Dec 10, 2009, at 4:06 AM, ralphschafermeier wrote:

>
>
> Hi folks,
>
> I am looking to use Unison for folder synchronization between a  
> Windows workstation and a Mac.
>
> Last August, someone posted on a forum that Unicode support is fully  
> functional in the development
branch:http://stayinsync.net/2009/04/enable-unicode-normalization-in-unison/comment-page-1/#comment-20 
> .
>
> Is this true? And if so, has it found its way a stable release in  
> the meantime (2.32.52 or earlier)?
>
> Sorry if I overlooked something, but I couldn't find any official  
> announcement regarding this.
>
> Thanks for any clarification!
>
> Best regards,
> Ralph
>
>
> 

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/unison-users/join
    (Yahoo! ID required)

<*> To change settings via email:
    unison-users-digest <at> yahoogroups.com 
    unison-users-fullfeatured <at> yahoogroups.com

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

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

Re: Unicode support status?

Re: Unicode support status?

> Ubuntu <-> Mac OS X seems to be fine, stable and works as required.   
> My
> Mac OS X filestore is case insensitive which is standard I believe.   
> The
> problems I do have with transfer to Mac OS X are to do with number of
> open files; basically Mac OS X does not have the capability of
> concurrently opening enough files for my task -- Ubuntu has no problem
> with basically the same transfer.

I haven't encountered this issue.  What goes wrong?

     - B

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/unison-users/join
    (Yahoo! ID required)

<*> To change settings via email:
    unison-users-digest <at> yahoogroups.com 
    unison-users-fullfeatured <at> yahoogroups.com

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

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

Re: Unicode support status?

On Thu, 2009-12-10 at 08:36 -0500, Benjamin Pierce wrote:
> > Ubuntu <-> Mac OS X seems to be fine, stable and works as required.   
> > My
> > Mac OS X filestore is case insensitive which is standard I believe.   
> > The
> > problems I do have with transfer to Mac OS X are to do with number of
> > open files; basically Mac OS X does not have the capability of
> > concurrently opening enough files for my task -- Ubuntu has no problem
> > with basically the same transfer.
> 
> I haven't encountered this issue.  What goes wrong?

I ask for a sync between Ubuntu server (the source) and Mac OS X client
(the destination) and there are large numbers of files to commit --
sometime 20,000+.  Some directories can have 1000+ files, e.g. Fortress
Subversion checkout.  This seems to trigger an inability to do a sync.
Too many open files is the error message.  By trimming the commit
manually to avoid the directories with >500 files and keeping the total
number of files to be processed <5,000 I get a sync.  But this can take
5 or 6 rounds of work, by which time I am getting grumpy (more grumpy
than usual 

There are no problems with syncs over twice this size where Ubuntu is
the client (destination) for the sync.

I am currently away from my MacBook just now so I cannot prepare a
proper error report.  If you point me at the bug reporting system, I am
almost certain I can prepare a more complete report.

If this problem has an easy solution, it would help me tremendously.

--

-- 
Russel.
=============================================================================
Dr Russel Winder      Partner
                                            xmpp: russel <at> russel.org.uk
Concertant LLP        t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,   f: +44 8700 516 084   voip: sip:russel.winder <at> ekiga.net
London SW11 1EN, UK   m: +44 7770 465 077   skype: russel_winder

Re: Unicode support status?

Benjamin,

On Thu, 2009-12-10 at 07:40 -0500, Benjamin Pierce wrote:
>   
> I'm not sure how many people are using the unicode support actively, 
> but in other respects the developer version seems very stable. 
> Anybody have any opinions on how well unicode is working now?
> 
> - Benjamin

I am not completely up to date from trunk, I'll update and build again
next week.  Ubuntu <-> Ubuntu has never been a problem using UTF-8
encoded Unicode file and directory names.  It used to work and it
continues to work.  On the other hand this doesn't need special support
in Unison and I am not sure I am using it.  So this isn't a real data
point.

Ubuntu <-> Mac OS X seems to be fine, stable and works as required.  My
Mac OS X filestore is case insensitive which is standard I believe.  The
problems I do have with transfer to Mac OS X are to do with number of
open files; basically Mac OS X does not have the capability of
concurrently opening enough files for my task -- Ubuntu has no problem
with basically the same transfer.

--

-- 
Russel.
=============================================================================
Dr Russel Winder      Partner
                                            xmpp: russel <at> russel.org.uk
Concertant LLP        t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,   f: +44 8700 516 084   voip: sip:russel.winder <at> ekiga.net
London SW11 1EN, UK   m: +44 7770 465 077   skype: russel_winder

apparently irregular behaviour of 2.32.12 under MacOSX

hello,

I have two issues with 2.32.12 as compared to the previously used 2.27.  
some feedback would be nice:

I'm currently running the binary provided at the unison home page  
(including GUI) but do
use only the command line interface.

I now observe two things

1.)

while with client/server OS = macos 10.4/10.6  everything seemed fine, I  
now observe with
the combination 10.5/10.6 (i.e. one machine upgraded from 10.4) the  
following:

starting the unison run on the 10.5 machine always produces this kind of  
message when using the CLI:

==========CUT==============

2009-12-11 14:45:57.010 Unison[54705:100b] *** _NSAutoreleaseNoPool():  
Object 0x209e20 of class NSThread autoreleased with no pool in place -  
just leaking
Stack: (0x95898dac 0x957c5e14 0x957cb3e0 0xaab4 0x2264 0x2178)
2009-12-11 14:45:57.019 Unison[54705:100b] Calling nonGuiStartup

==========CUT==============

this seems to have no adverse effect but I'm not completely sure: is this  
message irrelevant?
and what does it mean?

2.)

I believe the following is solely an issue of 2.32.12 as opposed to 2.27:

when syncing two roots whose pathnames contain blanks I can no longer use  
something like

unison -force 'rootnameWwith blanks'  someprev.prf

previously single quotes around the `force' argument where enough to  
protect the blanks in the pathname.
now unison parses this by splitting the argument at the blank and uses  
only `rootnameWith' as `force'
argument, which leads, of course, to
misinterpretation of the command line and to "fatal error...not one of  
current roots"

I tried additional backslash quoting but without success.

on the other hand, using

force = rootnameWith blanks

in the prf-file works as expected, so I have a workaround, but still...

regards,

joerg

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/unison-users/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/unison-users/join
    (Yahoo! ID required)

<*> To change settings via email:
    unison-users-digest <at> yahoogroups.com 
    unison-users-fullfeatured <at> yahoogroups.com

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

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