o u]X' @sdZddlZddlZddlZddlZddlZddlZddlZddl Zddl Zddl ZdZ dZ ddddde dddf d d Zddde ddfd d ZdS) a| Helper functions for working with tor as a process. :NO_TORRC: when provided as a torrc_path tor is ran with a blank configuration :DEFAULT_INIT_TIMEOUT: number of seconds before we time out our attempt to start a tor instance **Module Overview:** :: launch_tor - starts up a tor process launch_tor_with_config - starts a tor process with a custom torrc Nz ZZtordFTc  sJtjjrdurtkrtddntjj dkr+dur)tkr)tddt j j |vrJt j |r=td|t j |sItd|n tjj|sWtd||dtfvrit j |sitd||gd} } |ru| |7} |r|tkrtjd d d d } | d | g7} n| d |g7} |r| dtt g7} d} zztj| tjtjtjd} |r| jtjj|| jrՇfdd} ttj| t tj!t"#d} t"#d}d} | j$%&dd'}|std||r||| (|}|(|}|rFt)|*d |krF| WWrt+d| r5|r5| j$r,| j$| j,r5| j,| rEzt -| WSYSS|rd|.\}}d|vrdd|vrb|/dd'}|}q| rs| 0| 1r|t+d| r|r| j$r| j$| j,r| j,| rzt -| WwYww)aM Initializes a tor process. This blocks until initialization completes or we error out. If tor's data directory is missing or stale then bootstrapping will include making several requests to the directory authorities which can take a little while. Usually this is done in 50 seconds or so, but occasionally calls seem to get stuck, taking well over the default timeout. **To work to must log at NOTICE runlevel to stdout.** It does this by default, but if you have a 'Log' entry in your torrc then you'll also need 'Log NOTICE stdout'. Note: The timeout argument does not work on Windows or when outside the main thread, and relies on the global state of the signal module. .. versionchanged:: 1.6.0 Allowing the timeout argument to be a float. .. versionchanged:: 1.7.0 Added the **close_output** argument. :param str tor_cmd: command for starting tor :param list args: additional arguments for tor :param str torrc_path: location of the torrc for us to use :param int completion_percent: percent of bootstrap completion at which this'll return :param functor init_msg_handler: optional functor that will be provided with tor's initialization stdout as we get it :param int timeout: time after which the attempt to start tor is aborted, no timeouts are applied if **None** :param bool take_ownership: asserts ownership over the tor process so it aborts if this python process terminates or a :class:`~stem.control.Controller` we establish to it disconnects :param bool close_output: closes tor's stdout and stderr streams when bootstrapping is complete if true :param str stdin: content to provide on stdin :returns: **subprocess.Popen** instance for the tor subprocess :raises: **OSError** if we either fail to create the tor process or reached a timeout without success Nz/You cannot launch tor with a timeout on WindowsZ _MainThreadz@Launching tor with a timeout can only be done in the main threadz+'%s' is a directory, not the tor executablez'%s' doesn't existzA'%s' isn't available on your system. Maybe it's not in your PATH?ztorrc doesn't exist (%s)z empty-torrc-Tprefixtext-fZ__OwningControllerProcess)stdoutstdinstderrcs td)Nz+reached a %i second timeout without success)OSError)Zsignumframetimeout./usr/lib/python3/dist-packages/stem/process.pytimeout_handlers z#launch_tor..timeout_handlerzBootstrapped ([0-9]+)%z\[(warn|err)\] (.*)$z Timed outzutf-8replacezProcess terminated: %srzsee warnings abovez: )2stemutilsystemZ is_windowsDEFAULT_INIT_TIMEOUTr threadingZcurrent_thread __class____name__ospathsepisdirisfileZ is_availableNO_TORRCexiststempfilemkstempstrgetpid subprocessPopenPIPEr writeZ str_toolsZ _to_bytesclosesignalSIGALRM setitimer ITIMER_REALrecompiler readlinedecodestripsearchintgroupalarmr removegroupssplitkillwait)tor_cmdargs torrc_pathcompletion_percentinit_msg_handlerrtake_ownership close_outputr Z runtime_argsZ temp_fileZ tor_processrZbootstrap_lineZ problem_lineZ last_problemZ init_lineZbootstrap_matchZ problem_matchZrunlevelmsgrrr launch_tor%s -                       #    rFc Csz tj|tjjjk}Wn tyd}Ynwd|vrIgd}t|dtr/|dg|d<d} |dD] } | |vr?d} nq5| sI|ddd} t | D]\} } t| trc| d| | f7} qQ| D] }| d| |f7} qeqQ|rt |dd gd |||||| d St j d dd \}}z:t|d }|| Wd n1swYddg}t |||||||Wz t|t|WSYSz t|t|WwYw)a Initializes a tor process, like :func:`~stem.process.launch_tor`, but with a customized configuration. This writes a temporary torrc to disk, launches tor, then deletes the torrc. For example... :: tor_process = stem.process.launch_tor_with_config( config = { 'ControlPort': '2778', 'Log': [ 'NOTICE stdout', 'ERR file /tmp/tor_error_log', ], }, ) .. versionchanged:: 1.7.0 Added the **close_output** argument. :param dict config: configuration options, such as "{'ControlPort': '9051'}", values can either be a **str** or **list of str** if for multiple values :param str tor_cmd: command for starting tor :param int completion_percent: percent of bootstrap completion at which this'll return :param functor init_msg_handler: optional functor that will be provided with tor's initialization stdout as we get it :param int timeout: time after which the attempt to start tor is aborted, no timeouts are applied if **None** :param bool take_ownership: asserts ownership over the tor process so it aborts if this python process terminates or a :class:`~stem.control.Controller` we establish to it disconnects :param bool close_output: closes tor's stdout and stderr streams when bootstrapping is complete if true :returns: **subprocess.Popen** instance for the tor subprocess :raises: **OSError** if we either fail to create the tor process or reached a timeout without success FZLog)z DEBUG stdoutz INFO stdout NOTICE stdoutTrGz%s %s r-N)r ztorrc-rwZ__ReloadTorrcOnSIGHUP0)rversionZget_system_tor_versionZ RequirementZTORRC_VIA_STDINIOError isinstancer%appendlistitemsrFr#r$openr*rr+r9)Zconfigr>rArBrrCrDZ use_stdinZstdout_optionsZ has_stdoutZ log_configZ config_strkeyvaluesvalueZtorrc_descriptorr@Z torrc_filer?rrrlaunch_tor_with_configsV/       rV)__doc__rr0r,r'r#rZ stem.prereqrZstem.util.str_toolsZstem.util.systemZ stem.versionr!rrFrVrrrrs (