Theo v. Werkhoven wrote: Thanks for the reply.
Fri, 29 Apr 2005, by mrmazda@ij.net:
This SuSE 8.2 system has run 24/7 more than 2 years. hostname used to work, and the prompts would use it. Not any more, and I have no idea why, or when it broke, but it probably only broke within the past 3-8 weeks.
Which is why reboots aren't all that bad afterall, at least it gives a clue what break when and why.
Where do I look for clues in this case? Whatever may have been in the logs surely would have expired out by now? /var/log/warn does have various errors. April 4 was the last entry beginning with ax5t3 (nmbd). The rest start with (none) ("kernel: usb-uhci.c" is 1st entry, followed 13 seconds later by rpc.statd[1070] with a gethostbyname error). /var/log/YaST2/* have no entries on April 4. /var/log/messages has no entries near the time of the warn messages, but indicates I was doing some samba reconfiguration attempts about (a few hours after) that time.
#hostname (none)
#uname -n (none)
#uname -a Linux (none) 2.4.20-4GB #1 Fri Jan 14 15:08:13 UTC 2005 i586 unknown unknown GNU/Linux
#cat /etc/HOSTNAME ax5t3.ij.net
How is your /etc/hosts file?
It works on all the rest of my puters. It starts out with 127.0.0.1 localhost loghost and includes 192.168.100.52 ax5t3.ij.net ax5t3
#nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53
** server can't find ax5t3.ij.net: NXDOMAIN
Yout DNS server config seems to be broken.
"I" don't have a DNS server. 207.22.166.61 belongs to my ISP, which can't see past NAT. I use hosts to handle all local puters.
nslookup doesn't work on any of my puters. :-(
SuSEconfig also returns "unknown host". Timestamp on 13 byte /etc/HOSTNAME is Nov 2003. Various 1st lines in /etc/resolv.conf have no apparent impact.
Anyone have any idea how to fix this?
Systematically check all files involved, and next time use
"all files involved" means what? IOW, what files I've not mentioned are involved? I have other Linux and other puters, and haven't found any differences in files I've looked at that could account for this.
backups/logbooks when you make changes on a running system, without checking if it survives a reboot.
Backups are nice. I do it with the files I change. The problem is figuring out which/where are the files YaST and YOU change, and which have gotten broken by something unknown. -- "Love your neighbor as yourself." Matthew 22:39 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/