[scponly] won't someone _please_ think of the archives ? (scponly + unison + chroot)

[Ensel Sharon]

Ok, so it turns out I'm not the only person that has wondered if unison
can be made to run in an scponly chroot with an incoming dir:

https://lists.ccs.neu.edu/pipermail/scponly/2004-May/000532.html

and:

http://forum.textdrive.com/viewtopic.php?pid=43835

So ... obviously after three tries in two months, nobody is interested in
commenting to me about this, but for the sake of people googling two years
from now, can someone PLEASE confirm or deny that unison can be made to
work with an incoming chroot directory under scponly ?

At this point I really just want to know whether it is possible or not.

Thanks.


----------

(rehash of my third posting on this topic follows, for those just tuning
in)

I see on the web page and in the source that Unison works, and I further
see that there was a fix (relatively) recently added that fixes some HOME
variable issues.

However, I cannot get it to work.

scp, rsync, sftp, etc. - all work.

But Unison keeps trying to create .unison in the users home directory, as
defined by the underlying systems' /etc/passwd, but in reality the users
writeable directory is:

~/incoming

So I need Unison to create:

~/incoming/.unison

and not:

~/.unison

I see no way to do this from the unison command line.  Can anyone confirm
successful operation ?  Can anyone confirm successful operation in a
chroot with a incoming directory ?