Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
After taking over the RHEL admin responsibilities (while still being quite green), I am looking into our kickstart builds and noticed that there are "snippets" being used to enable a couple of services post-build.
When I looked, I noticed that these services (osad & nscd) are explicitly set to be enabled in the kickstart script.
I have not been able to find a log file or error message as to why these services are not being enabled without using the additional snippets.
Does anyone have any idea where I can find why these services are not enabled after a kickstart build unless I use an additional post-install script to enable them?
I looked all through the finished script and verified that there is no white space in the services line. In fact, originally, osad and nscd were the first two services listed (--enabled=osad,nscd,ntpd....) and I moved them to the end...just in case order had anything to do with it.
Also, I found no mention of osad apart from the above-mentioned "services" call and the insertion of the snippet that I still have to add that just does a "chkconfig osad on". Same goes for nscd.
We are a little behind on patching our Satellite server, so I don't know if that could have anything to do with it. We're going to get Satellite current on patching and everything, but that's a fairly major thing that tends to break lots of stuff, so we're not rushing into that. Who knows...maybe that's all it is.
I wondered about that as I was originally wondering if I was running into an issue of having too long of a string. We're using Satellite, so I don't know if there's a way to separate those out unless I just go directly into modifying the script manually. Not opposed to doing that, but I just think it shouldn't HAVE to be done that way. (I like when stuff just works the way it's supposed to.)
I can definitely try your suggestion, though. It might help to narrow down the cause of why it's not working the way I've got it.