unix
8 minpipefail, Signals, and Unix Process Management
Unix is full of tiny control primitives. Learn how `set -o pipefail`, process signals, and clean lifecycle management keep shell pipelines reliable and debuggable.
Search the library
59 matching resultsArticles and interview answers
unix
8 minUnix process inheritance: environment variables and file descriptors
Trace what survives fork and exec, and close capabilities a child should not inherit.
unix
8 minUnix Foundations: File Permissions, Ownership, and Descriptors
Understand users, groups, permission bits, file descriptors, and redirection so shell and service behavior is easier to debug.
unix
6 minUnix file publication: replace names without exposing partial bytes
Separate atomic visibility from crash durability when publishing local files.
unix
5 minUnix Log Sorting: Normalize Offset Timestamps Before Ordering Events
Build a bounded investigation pipeline that preserves malformed records and avoids lexical sorting across mixed offsets.
unix
7 minUnix Signals and Child Processes: What Your Service Must Clean Up
Follow signals from a container stop through shell wrappers and child processes, and build shutdown behavior that preserves work.
unix
9 mingrep, sed, and awk: Reliable Text Search and Small Stream Programs
Compose Unix text tools with explicit input, quoting, exit-status handling, and safe edits instead of treating pipelines as magic.
Q&A
Q&AWhat does a large TCP TIME_WAIT count mean?
TIME_WAIT is part of safe TCP teardown; verify actual ephemeral-port pressure before tuning sysctls.
Read the concise answer
TIME_WAIT helps prevent delayed packets from an old connection from contaminating a new one. A high count can be normal. Diagnose port exhaustion by checking outbound tuple reuse, NAT limits, ephemeral port range, and connection pooling. tcp_tw_reuse semantics vary by kernel and are not a universal first fix.