Bug 90221
Summary: | /etc/rc.d/init.d/mysqld isn't marked as a config file | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Nathan G. Grennan <redhat-bugzilla> |
Component: | mysql | Assignee: | Patrick Macdonald <patrickm> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-05-07 15:06:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nathan G. Grennan
2003-05-05 16:45:15 UTC
This is really working as designed. The init script is something that we control for that particular version of the package. It could contain modifications/additions that are not in your existing mysqld init script. Running your updated version with the old init script could cause problems. The other database that we support, PostgreSQL, handles the init script in the same fashion. I disagree when there is no way to do things that depend on a service other than putting in the init.d script. An alternative would be to have a set location that the init.d script would check for and call it if it was there. If you won't rethink you view, then highly consider this method. It fits within RedHat's style of /etc/xinetd.d, /etc/pam.d, /etc/cron.d, /etc/profile.d, etc. |