When started under systemd, the launcher now logs via the notify socket API when all configured WEBrick servers have started so the service state is reported accurately (rather than the daemonization point).
An example unit file is now shipped that uses a --no-daemonize argument to override the config file, so misconfiguration will not prevent the service from starting correctly.
Related issues
Feature #19480: Support systemd's notify service type, call sd_notify on startup
Added by Dominic Cleal about 7 years ago
fixes #19480 - add systemd notify support
When started under systemd, the launcher now logs via the notify socket
API when all configured WEBrick servers have started so the service
state is reported accurately (rather than the daemonization point).
An example unit file is now shipped that uses a --no-daemonize
argument to override the config file, so misconfiguration will not
prevent the service from starting correctly.