Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #32046
Closed
Open
Created Oct 11, 2019 by David Fifield@dcfOwner

Stop counting handlers

The transport programs (client, server, and server-webrtc) have some obsolete handler-counting code that tries to keep the process alive until all ongoing connections have terminated. This is a remnant of an earlier version of pt-spec that prescribed different handling of SIGINT and SIGTERM, and required this behavior on SIGTERM. pt-spec has since changed to no longer mention SIGINT, and prescribe immediate shutdown (terminating ongoing handlers) on SIGTERM.

Here's background: comment:5:ticket:26389.

Here's the corresponding change in meek: https://gitweb.torproject.org/pluggable-transports/meek.git/commit/?id=c7541223c704f76cb45a4e20bd20d963ea8d1fc7

Assignee
Assign to
Time tracking