Project

General

Profile

Actions

Feature #19480

closed

Support systemd's notify service type, call sd_notify on startup

Added by Dominic Cleal almost 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Core
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

The smart proxy launcher should support calling libsystemd's sd_notify API (or the equivalent, writing to the Unix socket) when daemon mode is disabled and the service is listening for requests.

This would allow it to support systemd's notify service type where the service is started in the foreground and notifies the service manager that it's ready before marking the service as up.

Using a notify/non-forking mode is preferable over daemonization as it simplifies setup, provides a more accurate service state (instead of marking the service up as soon as the fork occurs), and should allow systemd to capture stdout/err from the main server process.


Related issues 1 (0 open1 closed)

Related to Packaging - Bug #12463: The default settings of foreman-proxy conflict with it's systemd service unit.Resolved11/12/2015Actions
Actions #1

Updated by The Foreman Bot almost 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/525 added
Actions #2

Updated by Dominic Cleal almost 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Dominic Cleal almost 7 years ago

  • Related to Bug #12463: The default settings of foreman-proxy conflict with it's systemd service unit. added
Actions

Also available in: Atom PDF