Red Hat Bugzilla – Bug 296351
chkconfig resolves LSB dependencies to latest service when duplicate Provides exist
Last modified: 2014-03-16 23:08:35 EDT
Description of problem:
When chkconfig is deciding on the priority order using LSB dependency checking,
it uses the latest dependency value if there are multiple services that
'Provides' the dependency.
If you have a service that depends on $network, $network is provided by two
different services by default on RHEL 4, 'network' and 'NetworkManager'.
network has: chkconfig: 2345 10 90
NetworkManager has: chkconfig: 345 98 02
Due to this bug any service with a dependency on $network would end up as 99 01,
which causes other things that have a dependency on that service to have a problem.
chkconfig should resolve the dependency on the first service, not the last one
to prevent this.
Version-Release number of selected component (if applicable):
With the appropriate setup, it occurs every time.
Steps to Reproduce:
1. Copy the attached file to /etc/init.d/
2. Verify you have both network and NetworkManager on the system
3. Run chkconfig --add mysql
S99mysql and K01mysql are created in the appropriate places.
Earlier starting and later stopping. Without NetworkManager, I get K36mysql and
Created attachment 199571 [details]
Example init.d script which gets set to S99/K01 due to $network dependency
This is fixed in a later update by having NetworkManager no longer provide
$network. - we're not planning on changing chkconfig for RHEL 4 at this time.