Avi Kivity:

We are using systemd to supervise our NoSQL database [...]

Sometimes [it needs] to perform expensive operations during startup (log replay, rebuild from network replica) before we can start serving. Rather than configure a huge start timeout, I'd prefer to have the service report progress to systemd so that it knows that startup is still in progress.

That's something for your database software to address, not systemd. Perhaps you will have better luck than the person who tried to get this with MySQL for four years, and instead merely received a tweak of the server exit code and a closure of the bug. At least xe managed with MariaDB, though. (-:

 *

   MariaDB Server: MDEV-5713: RFE: Add support for systemd notify
   feature <https://mariadb.atlassian.net/browse/MDEV-5713>

 *

   MariaDB Server: MDEV-5536: Support systemd socket activation
   <https://mariadb.atlassian.net/browse/MDEV-5536>

 *

   MySQL Bugs: #65809: RFE: send a notify message to systemd daemon
   <https://bugs.mysql.com/bug.php?id=65809>

 *

   MySQL :: WL#7895: Add systemd support to server
   <http://dev.mysql.com/worklog/task/?id=7895>

 *

   6 thoughts on “MySQL 5.7 — Native Systemd Support”
   <http://mysqlserverteam.com/mysql-5-7-native-systemd-support/#comments>

 *

   better systemd integration
   <https://www.mail-archive.com/pgsql-hackers@postgresql.org/msg273121.html>
   pgsql-hackers, Peter Eisentraut, 2015
   <https://www.mail-archive.com/pgsql-hackers@postgresql.org/msg273121.html>

 *

   pgsql: Add support for systemd service notifications
   
<http://www.postgresql.org/message-id/e1aqne5-0003cj...@gemulon.postgresql.org>

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to