FS#32525 - [mysql] Write pidfile

Attached to Project: Arch Linux
Opened by Paul Gideon Dann (giddie) - Wednesday, 07 November 2012, 13:55 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 17 February 2013, 11:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Can you modify the systemd unit file so that mysql writes a pidfile? I'd like to monitor MySQL with Monit, and a pidfile is required in order to do this.

Additional info:
* mysql 5.5.28-1
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 17 February 2013, 11:50 GMT
Reason for closing:  Implemented
Additional comments about closing:  mysql 5.5.30-2
Comment by Andrea Scarpino (BaSh) - Wednesday, 07 November 2012, 20:16 GMT Comment by Paul Gideon Dann (giddie) - Wednesday, 07 November 2012, 22:05 GMT
Thanks; I'm able to do it myself, but would you mind explaining for me why you don't want a pidfile? Postresql has a handy pidfile I can use, as does php-fpm, and many others, and I don't think it's only the forking-type units. Is there a policy on this?

By the way, the Restart=always line is helpful; I've had to request that for other units, but I'm glad mysql already had it set.
Comment by Dave Reisner (falconindy) - Saturday, 10 November 2012, 00:54 GMT
What does monit do that systemd doesn't?
Comment by Paul Gideon Dann (giddie) - Saturday, 10 November 2012, 12:57 GMT
Monit tests that MySQL is responding via socket and TCP, and will send e-mails and optionally perform actions if the PID changes, or cpu or memory consumption reaches a certain level, etc. Systemd can replace Monit's restart-on-crash feature, but not the rest. I wish systemd could e-mail on unit failure. I suspect that might be in the pipeline, but I haven't checked.

Loading...