On 18-Dec-98, Peter (Troff) Petroff took time to write : > * No repeat no config changes WHATSOEVER.
at all, or only related to Apache, because.... > But the problem should never have occurred in the first place 'cause I > definitely didn't screw with it! ... it could happen if you change /etc/hosts or probably many other files. but i agree you have a strange case. however that one (Apache) seems ok now... even if we don't understand all details, it seems to be fixed. >> If Apache upon booting doesn't find the information in the DNS it needs, >> then >> it will dye. >> But if you relaunch it after that, it may work. > Never complained about DNS, just about its own local name. And repeated it's related. many apps (Apache, sendmail, etc...) needs to know during boot the name of the system they are on... so their using /etc/resolv.conf /etc/hosts, the dns specified, etc... to know that. Patrick.