Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
am new to linux, while booting this process continues , couldn't complete the booting process , guide me to stop this process, also help me find the file where all the services has been mentioned , so we can enable or disable the services we need during the system start up
The service that is holding you up is ypbind, located at /sbin/ypbind. It is the client service for NIS. It can be started different ways depending on your configuration. You will probably have to use a rescue CD, and boot from it, make the necessary changes, and then reboot again. ypbind can be started from either the /etc/rc.local file and/or chkconfig. You will also want to comment out any information in the /etc/yp.config file such as domainname and servername. This is assuming you don't want to use NIS. If you intend to use NIS, you will want to correct any inforamtion that may be incorrect in these files, such as servername or domain name.
I entered into rescue mode , as you said c couldn't find the files (configs) to edit and i have taken the info about the distro
is it possible to edit the configs and make changes to the files (through which we can enable specific services for each runlevels
example ,In init 2 certain services we can start additionally
and in init 3 , we should be able to stop some services
When you entered rescue mode (assuming this is a Red Hat based distro from the looks of the images) did you
before you took the screen shots? This takes the actual installed system and mounts it at /mnt/sysimage for editing. In rescue mode, when it dumps you to the shell, I am pretty sure you will be missing the specified system files because the resuce mode will not perform those options (such as: NIS functions, etc)
Once you perform the chroot, you have to find out what is starting the ypbind service and stop it. It could be many things or a combination of several things. Check the /etc/rc.local to see if ypbind is starting there (there will be a line with /sbin/ypbind). You can also edit the /etc/yp.conf file and remove the statement that defines the domainname and the NIS server. You should also be able to access chkconfig from here.