Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sponges
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • sponges
  • Issues
  • #5

Closed
Open
Created Jun 03, 2013 by Administrator@rootMaintainer

Add support for specifying the stop signal (or change default to term)

Created by: piotrb

I'd love for there to be a way to easily influence the signal sent at stop, right now it seems to be a choice between sigquit and sighup .. quit is quite brutal, if anything it should be sigterm, is not a common process management signal for many utilities, term is normally considered to be a much more graceful "ask the program to terminate", while quit is just an order to die. (also sigquit is meant to create core dumps, its generally not a good singal to use in an automated lifecycle)

If you can change from quit to term, that would satisfy this, or if not, just made an option in config allow to override the signal send on stop.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking