Bug 23021 - chkconfig values change request (S90 -> S78)
chkconfig values change request (S90 -> S78)
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: mysql (Show other bugs)
6.2
All Linux
low Severity low
: ---
: ---
Assigned To: Patrick Macdonald
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-12-30 02:44 EST by jve
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-12-30 02:44:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jve 2000-12-30 02:44:46 EST
The chkconfig line in the init.d script for mysql uses 90 for both the S 
and K sequence numbers.

The K number should be 10, but that's not the problem...

The problem is that the Apache httpd S number is 85, which means that 
Apache starts up before the internal database server (mysql), and for a few 
seconds (or however long it takes to get through any startup scripts from 
85 to 90), the apache CGI connections to Mysql fail because mysqld isn't 
running.

Can you please change the chkconfig S and K numbers in the Mysql init.d 
script to somewhere around 78 and 22?  That puts it before the externally 
accessible servers that start up in the 80's.

Thanks.
Comment 1 Trond Eivind Glomsrxd 2000-12-30 08:08:15 EST
We didn't ship mysql in Red Hat Linux 6.2 - where did you get it?
Anyway, for the version currently shipping in 7, the values are 85 (start) 15 (stop)

Note You need to log in before you can comment on or make changes to this bug.