Bug 26372
Summary: | MySQL fails to shutdown after password assigned | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | mcisar |
Component: | mysql | Assignee: | Patrick Macdonald <patrickm> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | zyglamail |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-06 22:52:16 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
mcisar
2001-02-06 22:52:11 UTC
The database system will always shut down when given a kill signal, which the shutdown will do... to work around it: Configure authentication in /root/.my.cnf or upgrade to mysql-3.23.32-5 from Rawhide, which uses a different shutdown mechanism. Please excuse my ignorance, but I am having the same problem. Documentation on your "workaround" of using my.cnf are slime to none so I can not seem to get that approach working. I also used "up2date" to check for an update to the mysql 3.23.32-1.7 I am running and nothing was reported. I then fired up gnorpm and found nothing more current than that version as well. Any additional info would be greatly appreciated. |