Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Iliya Manolov
  • slaposslapos
  • Repository
You need to sign in or sign up before continuing.
  • slapos
  • software
  • gitlab
  • instance-gitlab.cfg.in
Find file BlameHistoryPermalink
  • Kirill Smelkov's avatar
    gitlab: watcher should take care of sidekiq killed by SIGTERM · d14dc814
    Kirill Smelkov authored Jan 06, 2017
    The watcher should also watch for signals like SIGTERM killing sidekiq, which
    are trapped by sidekiq, with sidekiq exiting successfully (with exit code 0).
    
    To achieve this we rework our watcher-sigkill to be a generic watcher -
    that can be given a set of restart exit codes including signal names and
    monitors whether child process terminated with matching for restart exit
    code.
    
    Example usage:
    
    	watcher 0,SIGKILL prog ...
    
    Based on patch by @iv.
    Discussion: https://lab.nexedi.com/lab.nexedi.com/lab.nexedi.com/issues/25#note_22085
    d14dc814
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7