One way to trace the problem would be to add -x in the first line of /etc/rc.d/rc.sysinit and then boot.
So instead of #!/bin/bash make it #!/bin/bash -x
It will print each statement which is getting executed and when it stops, you will know at what command it hangs. That will give some indication as to what could be going wrong.
Amitay.
On Thu, 2003-10-30 at 22:33, Tushar Burman wrote:
Next LUG meet: 9 Nov 2003 around 4 pm - VJTI
Boys and girls,
I'm sick of this problem, and haven't found a solution for, uh.. ever.
Here's how it goes: Several of my servers have been compromised by worms at some point or other. I haven't had the time to do a complete post-mortem, but most seem to exploit SSH or Apache vulnerabilities. I've managed to clean up most without a complete reinstall (thank you apt-get!) but a few, including the most recent, don't seem to want to behave.
Even after cleaning the box up to the point that chkrootkit detects nothing, the system won't boot. It just stalls at "Setting hostname..." in the bootup sequence. Google groups shows this as a problem with several other folks as well, each using Red Hat 7.1/7.2 (mine's 7.2), but no answers are posted.
Has anyone else had this problem? Exasperated, I usually just reinstall the damn thing and patch like crazy, but I just don't have the time or inclination to do this again and again.
TIA
Tushar Burman Linux/BSD evangelist, RD350 rider, friend to animals Senior Writer, Network Computing Magazine Official: tushar_burman@jasubhai.com Y!: tusharburman MSN: tusharburman AOL: tusharburman ICQ: 112803958
All for freedom and for pleasure Nothing ever lasts forever Everybody wants to rule the world
Amitay.