The socks5 server runs from inetd. It is more efficient to run it as a standalone daemon. The optimum number of child processes highly depends on the capacity of the host system and the number of users accessing the server. Use the system command or the socks5 stopsocks script to send an HUP signal. After receiving an HUP signal, socks5 server re-loads the configuration file.
New connections use the new configuration file.
Stop a running socks5 server daemon stopsocks terminates a running socks5 server. If socks5 server does not behave as expected, review the debug log messages. The package also includes a dynamic client socksifier, runsocks, to dynamically socksify your client applications. The libsocks5.conf configuration file lets you control which socks5 server to use for different networks, different application servers, and different users. You may combine configuration methods.