cgconfig boot order prevents startup with NIS users in /etc/cgconfig.conf

Solution Verified - Updated -

Issue

In order to get cgconfig to start on boot, it needs to come up after ypbind, but the default order has cgconfig starting very early (which makes sense).

[root@lb0019 ~]# ls /etc/rc3.d/ | grep -P "cgconfig|ypbind"
S05cgconfig
S27ypbind

moving cgconfig to S28cgconfig and rebooting allowed it to come up fine on boot.
However, we are unsure about the potential negative consequences of having cgconfig start so late in the boot process.

Environment

Red Hat Enterprise Linux

6.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.