On Thu, 17 Sep 2020, Matthew Knepley wrote: > On Thu, Sep 17, 2020 at 8:33 PM Barry Smith <bsm...@petsc.dev> wrote: > > > > On Sep 17, 2020, at 4:59 PM, Satish Balay via petsc-users < > > petsc-users@mcs.anl.gov> wrote: > > > > > > Here is a fix: > > > > > > echo 127.0.0.1 `hostname` | sudo tee -a /etc/hosts > > > > Satish, > > > > I don't think you want to be doing this on a Mac (on anything?) On a > > Mac based on the network configuration etc as it boots up and as networks > > are accessible or not (wi-fi) it determines what hostname should be, one > > should never being hardwiring it to some value. > > > > Satish is just naming the loopback interface. I did this on all my former > Macs.
Yes - this doesn't change the hostname. Its just adding an entry for gethostbyname - for current hostname. >>> 127.0.0.1 MarksMac-302.local <<< Sure - its best to not do this when one has a proper IP name [like foo.mcs.anl.gov] - but its useful when one has a hostname like "MarksMac-302.local" -that is not DNS resolvable Even if the machine is moved to a different network with a different name - the current entry won't cause problems [but will need another entry for the new host name - if this new name is also not DNS resolvable] Its likely this file is a generated file on macos - so might get reset on reboot - or some network change? [if this is the case - the change won't be permanent] Satish