Re: Problem with sync on an ARM Mac

That's good advice.

meta:

 - this advice is written in terms of the command line.  If you aren't
   used to that, pause and learn it and then continue.  I'm kind of
   joking but really I have no idea how I could figure out what is
   really going on if I lived in a GUI-only world.

 - adopt the attitude that you can understand what is going on.

advice:

 - Don't guess that the hostname is changing.  Instead, see what it
   is. Just run `hostname` and see.  Wait a day and do it again.  On a
   7-year old intel mac that I have named foo, hostname returns
   "foo.local".  But I would not be surprised at foo.example.com, after
   connecting to a network with a DHCP esrver that announces example.com
   as the domain.

 - You can look at archive files to see what names where used.
   Basically "head -2" on ar[hash].  You can `ls -lt` to see mod dates.
   `head -2 ar*` is probably  enlightening.

 - 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.

 - sometimes there is a remote ssh process.  this is about using a root
   ssh://bar.example.org/path/to/stuff and then the local unison runs
   `ssh bar.example.org unison -server`, more or less.  In that case the
   remote unison will also determine a name.  So you may wish to set
   UNISONLOCALHOSTNAME in .ssh/environment if your shell environment
   files don't get run for incoming ssh commands.

 - another approach is to make the hostname (as returned by
   gethostname(3)) be stable, via network and dhcp config
   

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