commit daed7bca9f930e03a89ce8a4254e02a5310a0fc1 Author: Damian Johnson atagar@torproject.org Date: Wed Aug 12 15:41:46 2020 -0700
Present a safer pkill command
pkill's '-x' flag picks a process via an exact match rather than a regex. Caught thanks to uokf...
17:16 < uokf> I'd like to make a suggestion to change https://stem.torproject.org/faq.html#how-do-i-reload-my-torrc 17:17 < uokf> it says pkill -sighup tor 17:17 < uokf> but it should say pkill -x -sighup tor 17:17 < uokf> pkill sends the signal to all matching pids 17:18 <@arma> so if you have a process called 'extractor' then it'll hit that one too? 17:18 <@arma> that seems like a good bug. can you open a ticket for stem? i think atagar likes his tickets in github but i'm not sure. --- docs/faq.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/faq.rst b/docs/faq.rst index a7333fc7..50c9786a 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -444,7 +444,7 @@ Tor is configured through its `torrc you need to either restart Tor or issue a **HUP** for the changes to be reflected. To issue a HUP you can either...
- * Run **pkill -sighup tor**. + * Run **pkill -x -sighup tor**. * Send Tor a **HUP** signal through its control port...
::
tor-commits@lists.torproject.org