]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
More systemd service management cleanup
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Mon, 5 Feb 2018 07:37:44 +0000 (02:37 -0500)
committerTomas Krizek <tomas.krizek@nic.cz>
Fri, 16 Feb 2018 09:40:41 +0000 (10:40 +0100)
commit0398a9859855a6a4c6ec0c577e1368dc7230ae40
treef6764a1845a3a20a8ce20bad1c2a9f7a2b7998d7
parentb3e435e8e8b1d15920f86b09d61c6785700902d6
More systemd service management cleanup

Please see discussion at:
https://github.com/systemd/systemd/issues/8096

The new approach is:

 * non-templated kresd.socket and kresd-tls.socket, for the
   public-facing listening ports.  They know to invoke kresd@1.service
   if they're socket-activated.

 * kresd@.service *is* templated, to allow the admin to add more
   concurrent runners with:

      systemctl enable kresd@2.service

 * kresd-control@.socket is still templated, since each daemon has a
   separately-addressable different control port.

 * non-templated kresd.service is a dummy meta-service.  it is in the
   same slice as kresd@.service, and all the kresd@.service instances
   are PartOf= it, so you should be able to stop and restart all
   services together.  On systems like debian that ship
   /etc/init.d/kres, this also avoids having systemd-sysv-generator
   create a kresd.service based on the initscript.

 * no templated instances are explicitly instantiated during initial
   ship, but kresd@1.service should be socket-activated cleanly

Gbp-Pq: Name 0010-More-systemd-service-management-cleanup.patch
doc/kresd.systemd.7
systemd/drop-in/listen-tls.conf
systemd/drop-in/listen-udp-tcp.conf
systemd/kresd-control@.socket
systemd/kresd-tls.socket [moved from systemd/kresd-tls@.socket with 83% similarity]
systemd/kresd.service [new file with mode: 0644]
systemd/kresd.socket [moved from systemd/kresd@.socket with 85% similarity]
systemd/kresd@.service