terminal
18 posts found
Tracing Mystery Linux Processes and Open Ports with witr
A practical guide to diagnosing unknown processes, open ports, container runtimes, and socket conflicts on Linux servers using the witr CLI diagnostic tool.
The Evolution of Linux Process Triage: From Pipelines to Context Trees
Tracing rogue processes and open socket descriptors on Linux has evolved from manual procfs shell pipelines to unified context trees.
Tracing Process Ancestry and Orphan Daemons with witr
When an unexpected process binds a port or consumes memory, standard Linux tools show current state without explaining origin. Here is how witr reveals the full…
whoisthat: A Rust TUI VPN Client Backed by a Go/Xray Engine
whoisthat splits a VPN client into two processes: a Rust TUI for the terminal interface and a Go engine driving Xray-core underneath. This guide covers building…
Interview: Replacing Mermaid Slop with Semantic SVG Architecture Diagrams
Cathryn Lavery explains why automated graph renderers fail in production documentation, how strict density budgets eliminate visual clutter, and why standalone …
Managing Secure Remote Infrastructure with Oryxis
A step-by-step guide to configuring Oryxis, an open-source Rust SSH client with encrypted vault storage and port forwarding.
Why Is This Process Running? The Evolution of Process Provenance Tooling
How answering why a process is running moved from /proc archaeology to eBPF streams to witr, the open-source tool that makes provenance a single command.
Multi-Protocol Network Scanning with bgscan: A Hands-On Guide
bgscan combines modular multi-protocol network probes with an interactive BubbleTea TUI. Learn how to configure scan chains, execute targeted network discovery,…
Oryxis vs SSHPilot: Architectural Trade-offs in Modern Remote Shell Clients
A technical evaluation of Oryxis and SSHPilot, comparing local ChaCha20-Poly1305 encrypted vaults, GTK4 versus Rust runtime footprints, and peer-to-peer fleet s…
witr: Tracing Process Start Chains
ps and lsof show what is running, not why. witr walks the ancestry: PID to supervisor to the script that started it, in one chain.