Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 121
    • Merge requests 121
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Repository

Switch branch/tag
  • slapos
  • software
  • gitlab
  • watcher.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
watcher.in 1.8 KB
EditWeb IDE

Replace watcher.in

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7