Public bug reported:
On CentOS/RedHat el6, standard MySQL init script has the following
'status' code:
status)
status -p "$mypidfile" $prog
;;
In mysql56u-server package, you removed '-p "$mypidfile"' code, and that
makes script wrongly assume MySQL is running if any mysqld instance is
found on the machine.
This poses a problem if one runs MySQL through RedHat Cluster Suite, and
not through classic init script.
I'm attaching the patch that fixes the issue.
** Affects: ius
Importance: Undecided
Status: New
** Patch added: "mysql56u-init.patch"
https://bugs.launchpad.net/bugs/1390900/+attachment/4256551/+files/mysql56u-init.patch
--
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/1390900
Title:
mysql56u init script status doesn't check PID
Status in IUS Community Project:
New
Bug description:
On CentOS/RedHat el6, standard MySQL init script has the following
'status' code:
status)
status -p "$mypidfile" $prog
;;
In mysql56u-server package, you removed '-p "$mypidfile"' code, and
that makes script wrongly assume MySQL is running if any mysqld
instance is found on the machine.
This poses a problem if one runs MySQL through RedHat Cluster Suite,
and not through classic init script.
I'm attaching the patch that fixes the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/1390900/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ius-coredev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ius-coredev
More help : https://help.launchpad.net/ListHelp
