.TH stopsocks 1 "1 Oct 1998".SH NAMEstopsocks \- A script to manage standalone socks5 daemons.SH SYNOPSISstopsocks [-p \fIport\fP][\fIsignal\fP] [[\fIpid\fP]].SH DESCRIPTIONThe stopsocks script restarts and terminates standalone socks5 daemons. stopsocks is most useful for stopping preforked daemons. Use the command.PP.RS 5stopsocks -INT.RE.PPto stop all running daemons.  This will attempt to gracefully stop socks5.  If this is not successful, use the command.PP.RS 5stopsocks -KILL.RE.PPWhen you omit arguments, stopsocks attempts to send an HUP signal to the currently running socks5 daemon. The socks5 daemon stores its PID in /tmp/socks5.pid-{PORT}. You can change the filename that socks5 uses to store its PID with the --with-srvpidfile=\fIfilename\fP configure option or with the SOCKS5_PIDFILE environment variable..TP\fIport\fP.PPIdentifies the port number of the socks5 daemon. When you include the -p flag as the first argument, stopsocks uses the next argument as the port number..TP\fIsignal\fP.PPSpecifies the signal to send to the process. Valid values are 1 and 9:.RS 5.HP 4HUP - instructs stopsocks to re-read the configuration file..HP 4INT - interrupts the socks5 daemon.  Allows socks5 to gracefully stop..HP 5KILL - kills the socks5 daemon.  The kill signal cannot be blocked..RE.PPYou may optionally include PID with the signal argument. When you omit \fIpid\fP, stopsocks sends \fIsignal\fP to the currently running socks5 daemon..TP 5\fIpid\fPSpecifies the process that receives \fIsignal\fP.PP.SH SEE ALSOsocks5(1).PP.SH AUTHORNWSL SOCKS5 Development Team.brSend comments to socks5-comments@socks.nec.com