What problem does it solve? Scripts that bind to fixed, reused resource paths (Unix sockets, lock files, PID files) often leave orphaned processes behind when sessions end abruptly, causing silent pile-ups of stale listeners that break subsequent runs. ## Core Features & Use Cases - Self-cleaning startup pattern: Instructs scripts to find and terminate whatever process holds a reused resource path before unlinking or rebinding it, as the first step. - Unique-path preference: Recommends timestamp- or PID-suffixed resource paths per invocation when feasible, eliminating orphans entirely. - Correct socket-to-process mapping: Documents matching an AF_UNIX socket to its owning process via /proc/net/unix cross-referenced with /proc//fd/, warning that fileinode()/stat() on the socket file uses an unrelated number space. - Use Case: When writing a dev-server harness script that binds a fixed Unix socket, apply this guidance so each run kills the prior listener instead of accumulating orphaned instances over days. ## Quick Start Apply the resource-cleanup guidance when writing a script that binds a fixed socket or lock file so it terminates the existing holder before rebinding.
