According to Sony Lloyd Ponton: While burning my CPU.
>
> --------
> Linux redhat5.0
> Kernel 2.0.32
> -------
> Hi,
> My system boots with messages like:
> /etc/rc.d/rc3.d/s60usersd : .mydomain.com
> command not found
> /etc/rc.d/rc3.d/s60s91 httpd : .mydomain.com
> command not found
>
> then it hangs for 5 mins, before sending error:
> NWSER 0:Panic!!
> cannot get auto internal net with help of gethostbyname
>
> Starting SMB services: smbd httpd:cannot determine localhost
> name..
> Use servername to set it manually
> hp=0! connection timed out..
> and my system completely stopped at that level of booting.
>
> Question: I really dont wanna loose all my datas on my linux box. pls..
> help me to find out a way to boot my system again by not
> havin to reinstall from scratch..A long time ago..someone ..in the same
> case..was talkin about reinserting the install cd..but instead of
> reinstallin
> , there woudl be a way of gettin into the system, gettin rid of anythin
> referrin to
> httpd..smbd(any of these things that stop my system at boot)..anyway, if
> anyone can help
> me to go through that..I ll appreciate.
>
> Also if U could xplain me what is going on??
>
Possable cause(s)
Your system cant access a DNS server to resolve hostnames, possable
cause's for that are no connection to an ISP, no nameserver defined in
/etc/resolv.conf or localhost not in /etc/hosts or enterd incorectly.
The error message "/etc/rc.d/rc3.d/s60usersd : .mydomain.com" would stronly
suggest you have not edited /etc/resolv.conf or a /etc/hosts
misconfiguration for localhost.
Or misconfiguration of SMBD HTTP config files.
To get the system going use a rescue disk or a boot/root disk combination,
in other words the disk's you made before you installed Redhat-5.0 in the
first place. Read the instructions written to your screen at boottime when
using the disk(s).
If you have LILO installed as a boot loader you could try entering "linux 1"
as a parameter at the LILO prompt. That might start the sysem up in
run-level 1.
When you are in remove the symlinks which are producing the error messages
with rm S60xxxx, where S60xxxx is the offending daemon name.
There is no need to even think about reinstalling.
--
Regards Richard.
[EMAIL PROTECTED]
