Re: Can unison better help with renamed hosts?

On 24.04.24 14:06, Greg Troxel wrote:
> Tõivo Leedjärv <[email protected]> writes:
> 
>> On Wed, 24 Apr 2024 at 13:41, 'Mario Emmenlauer' via unison-users
>>> Do I understand correctly that unison will call gethostname(3) on each
>>> host, and use that for the names? That confuses me, because gethostname
>>
>> That is correct (unless overridden).
>>
>>> on the remote machine should not change, depending on whether I'm inside
>>> or outside the company network. The server always reports the same when
>>> you call hostname, no?
>>
>> It would appear that in your case it doesn't. But adding -showarchive
>> on the command line should help you debug the issue at least.
> 
> I always recommend debugging using the simplest query possible, as close
> to the source of possible confusion aspossible.  I also recommend not
> making assumptions, even things you think you know must be true.
> 
> Given that we have implicated, but not 100% reliably, a change in
> gethostname(3), it seems clear that Mario should run hostname(1) on this
> computer when it is in various places on the network, and actually see
> what values are printed.


This is indeed a good validation to make! But I checked, from inside and
outside the network, and the same values are printed:

#> hostname
bool
#> hostname --fqdn
bool.domain-name-here.de

 From my many years of using unison, I'm heavily surprised that gethostname
should be the main means to compute the archive checksum. I was often
confronted with the problem that inside vs. outside of a LAN, unison will
not keep the archive name. My money would have been on nslookup or something
like this being involved...

All the best,

     Mario

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