Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hello All,
I have Red hat linux enterprise edition installed in my server.and it was working fine.Now whenever I start it is booting well,all the services are started but the login prompt does not appear.
before somedays I want to execute a shell script at bootong time.some one tell me that enter a line for your shell script at the end of /etc/rc.local file..i have done this.
so i think thats why it is creating problem.
kindly suggest me how can i remove this problem.
I am using grub as a boot loader.
Thanks All,
-Rajendra
Enter details about your root partition when asked
Do, "chroot /mnt/sysimage" (without quotes)
Edit the file you want and reboot
You can also boot Knoppix or any other Live CD, access you RHEL root partition and make the changes.
Thnaks for reply but i don't want to change the file again,I need the solution for the above problem,I don't want to edit the rc.local file.what is the resion for occuring this problem
It seems like you did not put an "&" at the end of your commands in rc.local, so the terminal is occupied and the startup process will not progress to the next phase until you background the job thats occupying the terminal. If this is the case you need to fix your rc.local and the method above enables you to access your machine to edit the file.
I am sorry if I misunderstood you the first time. I thought you suspected that there was a problem with your rc.local and you were looking for a way to fix it.
It seems like you did not put an "&" at the end of your commands in rc.local, so the terminal is occupied and the startup process will not progress to the next phase until you background the job thats occupying the terminal. If this is the case you need to fix your rc.local and the method above enables you to access your machine to edit the file.
I am sorry if I misunderstood you the first time. I thought you suspected that there was a problem with your rc.local and you were looking for a way to fix it.
Thanks a lot,u didn't missguide me...thanks again
-Rajendra
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.