Re: Can unison better help with renamed hosts?

On 24.04.24 13:49, Tõivo Leedjärv wrote:
> On Wed, 24 Apr 2024 at 13:41, 'Mario Emmenlauer' via unison-users
> <[email protected]> wrote:
>>
>> I may have created some confusion about this. For my specific problem,
>> and other people may see this differently, I only care what host name
>> unison detected. I can easily take responsibility that the login to
>> the remote host works, because these errors are well explained in the
>> unison (or ssh) error messages. But _after_ unison logged into the
>> remote host, it does some magic (explained by you below, I see) to
>> check if the detected host name and the expected host name match. This
>> part is a black box for me, and not easy to understand/debug.
> 
> I was not precise enough. I did have in mind exactly the scenario you
> mentioned. Even after the connection has been established, Unison
> won't know what it's expected to have as the hostname. How could it?


This part still confuses me. I do not need unison to know what it's
expected to have as the hostname. I'm perfectly happy that it prints
what it detected as the hostname, that's all I would need. It may then
see that no archive for this (detected, and printed) hostname exists,
and may happily exit in error.

With the printed value, I can go ahead and check _why_ an unexpected
hostname was found. Was I connected to the wrong machine? Was there
an unexpected network change? Is hostname behaving strangely on the
server? Is it a bug in unison? All I would need to follow this up is
the printed value, to help me understand the root cause.

Or am I on the wrong track here?

All the best,

     Mario

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