Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
meek
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
    • A
      Anti-censorship
  • Pluggable Transports
  • meek
  • Issues
  • #24642

Closed
Open
Created Dec 15, 2017 by Mark Smith@mcs

cannot use TOR_PT_EXIT_ON_STDIN_CLOSE with meek-client-torbrowser

I am using meek built from the 0.28 tag on macOS.

If I add TOR_PT_EXIT_ON_STDIN_CLOSE=1 to the environment and start meek-client-torbrowser, the meek-client process that is started exits immediately. It generates this message on its way out: synthesizing SIGTERM because of stdin close I think this happens because meek-client-torbrowser does not attach stdin to anything when starting meek-client.

I am not sure how best to fix this. One approach would be for meek-client-torbrowser to remove TOR_PT_EXIT_ON_STDIN_CLOSE=1 from the environmnt before starting meek-client (since meek-client-torbrowser already handles TOR_PT_EXIT_ON_STDIN_CLOSE=1 on its own).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None