[tor-commits] [meek/master] meek-client-torbrowser no longer has special handling for SIGINT.
dcf at torproject.org
dcf at torproject.org
Thu Feb 7 22:35:30 UTC 2019
commit bbe789add5ece1d493f065ff0d0b125b0c2a6c78
Author: David Fifield <david at bamsoftware.com>
Date: Thu Feb 7 15:21:17 2019 -0700
meek-client-torbrowser no longer has special handling for SIGINT.
Since 0ec986eb2b4bc23d81e6e8beffd382890f55bfb1. This is the case with
all pluggable transports now.
---
meek-client-torbrowser/meek-client-torbrowser.go | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/meek-client-torbrowser/meek-client-torbrowser.go b/meek-client-torbrowser/meek-client-torbrowser.go
index 5c5316a..2daa108 100644
--- a/meek-client-torbrowser/meek-client-torbrowser.go
+++ b/meek-client-torbrowser/meek-client-torbrowser.go
@@ -391,14 +391,4 @@ func main() {
if err != nil {
log.Print(err)
}
-
- // If SIGINT, wait for a second SIGINT.
- if sig == syscall.SIGINT {
- sig := <-sigChan
- log.Printf("sig %s", sig)
- err = logSignal(meekClientCmd.Process, sig)
- if err != nil {
- log.Print(err)
- }
- }
}
More information about the tor-commits
mailing list