Search Results for "keep%20alive"

Shadowsocks-libev is a lightweight secured SOCKS5 proxy for embedded devices and low-end boxes. Shadowsocks-libev is written in pure C and depends on libev. It's designed to be a lightweight implementation of shadowsocks protocol, in order to keep the resource usage as low as possible. Snap is the recommended way to install the latest binaries. You can build shadowsocks-libev and all its dependencies by script. The latest shadowsocks-libev has provided a redir mode. You can configure your Linux-based box or router to proxy all TCP traffic transparently, which is handy if you use an OpenWRT-powered router. ...

...Convenient remote debugging of mobile phone page, packet capture tool, supports HTTP/HTTPS, no need for USB connection device. One-stop page debugging and packet capture tool. Remote debugging of any mobile phone browser page, any mobile terminal webview (such as WeChat, HybridApp, etc.) Keep the phone and PC under the same network (for example, connect to the same Wi-Fi at the same time). Enter the command line spy-debugger, follow the command line prompt to open the corresponding address with a browser. Set the HTTP proxy of the mobile phone, the proxy IP address is set to the PC's IP address, and the port is spy-debuggerthe startup port (default port: 9888), and then, install the certificate on the mobile phone. ...

...This is invaluable for post-mortem diagnosis of production daemons where reproducing a bug in a dev shell is impractical. pyringe can inject arbitrary Python into the target process, enabling on-the-spot logging, state dumps, or gentle patching to keep a system limping along while you gather evidence. It’s also useful for forensic snapshots: enumerate objects of a certain type, find reference cycles, or measure memory pressure without pre-instrumentation. While powerful, it’s designed for careful, auditable use—showing exactly what code runs and where—so teams can regain visibility when black-box processes go sideways.

A facility to keep a history of context information during runtime and then dumping it in a separate file when a problem occurs (similar to core dump).