NIS on RedHat

[ommy]

Hello...everyone, I have some problems here with my Linux Box. and I was wondering if someone could answer these questions.
I have Red Hat 7.2 on my machine.. I tried to configure NIS server on my machine but somehow, NIS cannot be configured. The problem it caused is that on booting the machine it starts listening to an NIS domain(which is not obviously there)..it takes a few minutes in this process. Now when it fails to listen to NIS...it switiches to runlevel 3 instead of booting into runlevel 5. I stopped 'YPBIND' and 'YPSERV' daemons, but every time you boot the system it starts listening to NIS , which, eventually fails(and it takes lot s of time to do so and delays bootig process). Now I want to stop these services so that these daemons does not invoke during the booting
process as well. Can anyone help me out with this? and please do let me know any Linux forums where I can post my "HOW-TO" questions...
Thank you
Ommy

[groovicus]

First thing I would do is either delete this post and move it to the OS section of the forums, or if you can't figure out how to do that, ask MsMittens to do it for you. You're asking a question that deals more with operations issues.

Try http://www.google.com/linux... not specific to your question, but it narrows your search results..

Once you get to the aforementioned section of google, type in "forms" or "bulletin boards" or "tutorials"....

Or do a search specific to your problem. Chances are that if you are having an issue with something, somebody else probably already did also, and had their question answered.. (kind of like here)

EDIT: Also, check out the search feature of AO... resources for Linux have been discussed many times, and many links have been provided.

[owensleftfoot]

Try "chkconfig ypserv off" without the quotes.

[Info Tech Geek]

I found some great information on the Linux Documentation Project (www.tldp.org) Website.

[extremez]

Boot the run level 3, then try running /etc/pam.d/authconfig (not positive on the path, don't have linux running where iam) but when you get it running it'll have a blue screen wizard. Set it not authenticate off any servers, just linux shadow passwords. Then restart, see if it boots up ok. If that doesn't help, or you use pam.conf and don't have the above dir, then post more information about the problem.

[owensleftfoot]

/etc/pam.d/authconfig is just the pam permissions file for running the authconfig program. The actual program is /usr/bin/authconfig or /usr/bin/authconfig-gtk for the x version.

[cgkanchi]

Editing one of the rc files (rc.3?) and removing (commenting out) the lines that say yp*should do it.
Try this:
cd /etc/rc.d
grep yp rc.*
It'll tell you which file(s) has the commands.
Just add a # at the beginning of those lines and reboot.

Cheers,
cgkanchi

[groovicus]

Ok, now for my question..

Editing one of the rc files (rc.3?) and removing (commenting out) the lines that say yp*should do it.
Try this:
cd /etc/rc.d
grep yp rc.*
It'll tell you which file(s) has the commands.
Just add a # at the beginning of those lines and reboot.


Boot the run level 3, then try running /etc/pam.d/authconfig (not positive on the path, don't have linux running where iam) but when you get it running it'll have a blue screen wizard. Set it not authenticate off any servers, just linux shadow passwords.

Being as how I am a linux newbie, I'm curious as to what your assesment of the problem is, and what (each of you) are trying to accomplish by doing the above? I am assuming that you have run into this type of problem before? Just trying to get some clarification...never know when I may need the information. :)

[tabich]

People were telling you that your machine is attempting to authenticate using yp, because it is still in the authentication configuration. And, that even though you stopped a yp service, it may have come back after a reboot, unless you stopped it from starting.,

Make sure the yp services do not start on boot( that was editing th rc files, and also, the easier way on redhat anyway "chkconfig ypserv off" as owensleftfoot said).

Make sure that your machine does not try to use NIS for authentication( authconfig).

You need to run authconfig as root, and unselect anything which mentions NIS, then run

chkconfig --list

and look through it to find all of the NIS related services which are scheduled to start in runlevel 5 or 3,

and then run

chkconfig <servicename> off

for each of them, I think the following are the NIS services you will need to turn off

chkconfig ypserv off
chkconfig ypbind off <----------------- I think this one, along with autconfig change, solves problem.
chkconfig yppasswd off

You can also turn off portmap unless you are using nfs...

chkconfig portmap off

[extremez]

Originally posted here (http://www.AntiOnline.com/showthread.php?threadid=253332#post709623) by owensleftfoot
/etc/pam.d/authconfig is just the pam permissions file for running the authconfig program. The actual program is /usr/bin/authconfig or /usr/bin/authconfig-gtk for the x version.

You are correct but I think i mention pam because I was picking up on his not being able to boot to X but still get to level3. Sometimes there are PAM issues specifically with run level5.

[cgkanchi]

groovicus:
if you're familiar with Windows 9x/DOS, you will know that there is a file called autoexec.bat that runs on boot. Any programs that are specified in that file run at boot. Similarly, you have the rc files in *NIX. You have at least one for each runlevel (someone correct me if I'm wrong here). They are named rc.1, rc.2,rc.3, etc. for runlevels 1,2,3, etc.

In case you don't know what runlevels are, without going into too much detail, runlevel 1 is single user mode, runlevel 3 is multiuser text mode and runlevel 5 is GUI (X Windows) mode. You can change runlevels by running the init command followed by the runlevel number (eg: init 3) as root.

Also, I asked him to put a # in front of the lines that contained yp* because that comments them out (i.e. they aren't interpreted by the OS). This is generally a better practice than deleting the line because it allows you to get things back to normal in case you mess up by just removing the # that you added rather than reconstruct the command.


Cheers,
cgkanchi