Shadowsocks client centos1/3/2023 ![]() ![]() I choose to use systemctl to manage the systemd instances of shadowsocks-libev. As a result, this kind of multi processes should only introduce slight overhead and even works well for low end boxes. Furthermore, this approach enables us to manage users with legacy control panels, for example old SSH / VHOST panels with each user’s ss-server running in its own space.Ĭompared to other implementations, shadowsocks-libev uses much fewer resources (about 1MB memory and hundreds of file descriptors in a typical usage). For example: 1Īs the best practice we recommend for shadowsocks-libev, it helps to isolate each user in different processes and reconfigure each user’s port/password/encryption/timeout without reload/restart the whole service. Actually you can use multiple instances instead. Sorry, we have no plan to support multi port configuration. And I also need to support the usage of multiple users. According to Madeye’s reply to the GitHub Issue, shadowsocks-libev does not support multi-port configuration: 1Ĭurrently I am using shadowsocks-libev, which is the libev port of shadowsocks. The original Python release of shadowsocks supports multiple users through configuration, by assigning different passwords on multiple ports. $ ln -sf libmbedcrypto.so.1 libmbedcrypto.so.0Ĭonfigure Multiple Users for Shadowsocks-libev Ss-local: error while loading shared libraries: libmbedcrypto.so.0: cannot open shared object file: No such file or directory Shadowsocks is an open-source encrypted proxy project, ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |