Project

General

Profile

Actions

Feature #7331

closed

[Deployment] Add systemd unit definition to the keepproxy package

Added by Brett Smith over 8 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
-
Story points:
2.0

Description

Functional requirements:

  • The definition should always be installed somewhere under /usr/share/doc/keepproxy.
  • On distros we support that ship with systemd (currently just Debian 8), the package installs the unit definition on the system.
  • Users should not need to edit this file to make configuration changes. Instead they should make changes to a file in /etc/default (on Debian) or /etc/sysconfig (on Red Hat) which are respected by the unit definition.
  • We want this to be as close as possible functionally to what we currently do under runit—whether that's thanks to runit features, or stuff we arrange in our runit script.
  • We want Restart= to automatically restart the daemon in most cases. See systemd.service documentation
  • We want StandardOutput= to move output to syslog or similar. See systemd.exec documentation

(some other background: http://www.kibinlabs.com/systemd-logging-tricks/)


Related issues

Related to Arvados - Feature #6034: [Deployment] Add sysvinit script to the keepproxy packageRejectedNico CĂ©sar10/14/2015Actions
Actions #1

Updated by Brett Smith over 8 years ago

  • Description updated (diff)
Actions #2

Updated by Ward Vandewege over 8 years ago

  • Description updated (diff)
Actions #3

Updated by Brett Smith over 8 years ago

  • Description updated (diff)
Actions #4

Updated by Brett Smith over 8 years ago

  • Target version changed from Arvados Future Sprints to Kanban
Actions #5

Updated by Tom Clegg almost 7 years ago

  • Status changed from New to Resolved
Actions #6

Updated by Peter Amstutz over 4 years ago

  • Target version deleted (Kanban)
Actions

Also available in: Atom PDF