Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Avoid system stability issues on roaming machines System
There is a case where if your plug your machine into several networks without rebooting, your machine could become unstable. In my case, this was due to the fact that on one of the networks I use, I have a static IP, and the IP has a hostname assigned in DNS both forward and reverse. Mac OS X is clever enough to do a lookup on the IP it has on any given network, and automatically set the hostname based on this ... however, it seems that a lot of applications get very confused if the hostname changes, with the effect that when you move from one network to the next, applications take a long time to start and/or they lock up, requiring a restart. Restarts sometimes don't complete, requiring a hard reset (and a subsequent disk check). Nasty. For me, it was changing between the hostname I have on one network, and the hostname I have set in the Network control panel.

I've not confirmed this with anyone else, but I was able to fix the problem on both my previous powerbook and my current 17" by editing the /etc/hostconfig file.

Simply su to root, and then edit the /etc/hostconfig file, changing the HOSTNAME variable from -AUTOMATIC- to anything you like (the same as what you have set in the Network control panel is sensible). Next time you reboot, the hostname will be set, and won't change when you move networks, with the benefit that your machine will become more stable. Don't ask me why this works, it just does.

[robg adds: Can anyone confirm? I have a PowerBook that only roams between two locations, but there's no name lookup activity going on, and it seems quite stable as is...]
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (1 vote cast)

Avoid system stability issues on roaming machines | 1 comments | Create New Account
Click here to return to the 'Avoid system stability issues on roaming machines' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Avoid system stability issues on roaming machines
Authored by: lailoken on Jun 10, '03 06:53:36PM

Another possible solution could be that a mounted SMB filesystem was present at the previous location.

Since SMB uses NFS underneath, it really tries to maintain the integrity of the mounted share and it's data (very unlike SMB). To this end when an app acceses a file on that share, or if there are unwritten data still waiting to get flushed to that network drive, the machine and/or tasks may delay or block totally and you can only kill them with grat difficulty.

The answer is to make sure you unmount all network drives from the clients and servers before putting your computer to sleep and taking it to a foreign network.

Hope this helps... I've still got lots to learn of Apple computers, but my unix is okayish.

[ Reply to This | # ]