[scponly] unsion (still) failing over scponly due to locatio of .unison

[Ensel Sharon]

I'm sorry for the repost - I just don't see how to make this work nicely
... perhaps creating a local home to match the scponly home really is the
right way to do it ?  It seems wrong...

-----


So everything seems to be set up properly for unison ... easy.

But when someone:

unison . ssh://user@host//chroot

It fails because it wants to put .unison in /, but they don't have access
to / because they are chrooted to //chroot


> Fatal error: exception Util.Fatal("Cannot find canonical name of
> /path/to/chroot/.unison: unable to cd either to it
>
> (/path/to/chroot/.unison: No such file or directory)
> or to its parent /path/to/chroot
> (/path/to/chroot: No such file or directory)")
> Fatal error: Lost connection with the server


I think I can work around this by setting the environment variable UNISON,
but then I need to create that same directory structure on my client
machine, so that seems like a kludge.

What is the right way to do this ?

Thanks.


_______________________________________________
scponly mailing list
scponly at lists.ccs.neu.edu
https://lists.ccs.neu.edu/bin/listinfo/scponly