Re: Problem with sync on an ARM Mac

Maybe I'm missing something, but I think if you change the hostname without
updating the unisonlocalhostname, everything should still work fine. For
myself, since the first time of needing to set unisonlocalhostname, I
always do it - so this would just make it more convenient (and avoid the
confusion when the problem of a changing hostname first crops up). Sure - a
UUID would be fine, but the hostname is the obvious memorable label.

Multiple users would have multiple archives, so each, potentially, could
name the host as they like - just as they can with UNISONLOCALHOSTNAME.


On Thu, 9 May 2024 at 01:47, Dale R. Worley <[email protected]> wrote:

> Greg Michael <[email protected]> writes:
> > Maybe on the first run of unison, the current hostname (perhaps editable
> > before saving) could be written to a file 'unisonlocalhostname' together
> > with the other archive files, and therafter taken from there. Should be
> as
> > stable as the archive.
>
> I think that could easily cause more trouble than it solves.  Because if
> one then later deliberately changes the name of the host, the recorded
> name doesn't change, which might be easy to forget, it invalidates the
> principle "Unison records things based on the host name".  Also, if
> there are multiple users, each user has a separate
> ~/.unison/originalhostname file with possibly different contents, and
> also it's not clear the best way to make this operate symmetrically
> between the host running Unison and the remote host.
>
> If you want to pursue this concept, I'd suggest recording not the
> current hostname but a UUID and calling it a "host identity" or better a
> "sync identity" because they'd be different for different users (or
> really, different .unison directories).
>
> Dale
>

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