Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 450
    • Issues 450
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 75
    • Merge Requests 75
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #159

Closed
Open
Opened Oct 12, 2018 by Adam Osuchowski@adwolGuest

Kea daemonization

There are some best practices on how unix daemons should behave. Some of these are not met on Kea. You can read little old but still up-to-date howto document for general overview how to linux daemons should work: http://www.netzmafia.de/skripten/unix/linux-daemon-howto.html

In particular:

  • Kea should put its daemons into background, not stay foreground
  • daemons should unbind their stdin, stdout and stderr from current streams (i.e. terminal) and bind them to /dev/null or alternatively stdout and stderr may be binded to log file
  • daemons should release their controlling terminal (setsid) because they don't communicate with users this way
  • daemons should change current working directory to root (/) not to lock any possible mount points
  • daemons should ignore all signals which is not significant to it (i.e. SIGPIPE)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Kea2.x
Milestone
Kea2.x
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#159