Comment 1 for bug 1396757
Revision history for this message
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@Jay,
The 'garbage' is due to the fact that mysqld is SIGkilled but its PID file still remains, so the script waits for it upto timeout (900s) and then exits. This is same behavior as 'service mysql stop'. So, removing the stale PID file should also do.
In any case, I have modified it to check for this and mysql-systemd will exit early.
On a long term, this can be fixed by replacing mysqld_safe and calling mysqld directly in unit file. That should avoid any need for these pre/post scripts.