Re: Problem with sync on an ARM Mac

"Stefan M. Moser" <[email protected]> writes:

> Dear Greg,
>
> Thanks!
>
>> - Stefan's question about client server is a good one.   I think both
>>   UNISONLOCALHOSTNAME and clientHostName are used when an ssh process
>>   obtains its canonical name.   So if you are syncing from one local
>>   path to another, with no remote unison, it's probably the same name.
>
> I think this part of the discussion relates to the discussions a few
> days ago regarding whether or not to introduce a serverHostName
> preference. If I understand you correctly, clientHostName is used for
> the name on the remote machine that is contacted by ssh.

I think clientHostName affects the name used by the unison process that
reads it as part of a profile.  That would be the originating one.  The
remote unison is a server process and as I understand it does not read
any profiles.  (But I use scripts that invoke unison with two roots, and
don't use profiles personally.  Yes I know that's odd.)

> This is
> exactly NOT what I need, actually. The remote host has a stable name
> (otherwise I couldn't contact it with ssh anyway),

do not confuse

  `ssh foo.example.com` will get you to the machine you call foo

  when you run `hostname` on foo, you always get "foo.example.com"

they might well go together.  But they are different conceptually and
might not.  The first one might as an example be implemented with all
sorts of crazy proxyjump and tunneling ssh stuff.

> but the local
> machine (i.e., the laptop) keeps changing name depending on which
> network I am on. I have been using UNISONLOCALHOSTNAME for decades
> already to fix the names on all machines once and for all. But the
> setup of this is rather annoying as can be seen from my lengthy
> desciption, so I would LOVE to use an option in the unison prf-file
> instead.

Try it.  Look at the ar files with head -2 ar*, and really just at the
one that got created by mod time.  Don't guess, and instead inspect.

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