ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #unix
Fork duplicates process state cheaply via copy-on-write and shares file descriptors by reference; exec is what makes that copy safe to run a different program.
A process with free CPU available but no progress often has a wrong nice value. Here's how to check the NI column, trace where the priority came from, and fix it with renice, nice, or systemd.
Unix fork-exec preserves file descriptors by design, which can lead to security leaks. Learn how to use FD_CLOEXEC and strace to manage descriptor inheritance and prevent resource leakage.
Learn how Unix shell pipelines work, see a practical example, and discover limits and common mistakes to avoid when chaining commands.
Guide to picking ash, dash, bash, or zsh as the default shell in minimal Unix containers, covering size, POSIX compliance, interactive features, and validation steps.
The Unix pipe is a kernel-buffered byte channel, not a temp file. Learn what the shell really does with |, how backpressure synchronizes stages, and why exit codes lie without pipefail.
A decision guide comparing cron, systemd timers, and at/batch for scheduled tasks on Unix‑like systems, with a concrete systemd timer example and verification steps.
When you’re hunting down a bug in a 10‑GB log, Less can be more than a pager. Learn how to toggle line numbers, jump to patterns, and chop long lines to keep your view stable, with real commands, trade‑offs, and a practical example.
File descriptors are the kernel’s integer handles for open resources. This post explains how they work, why close-on-exec prevents leaks, how to inspect them via /proc, and how to pass them between processes.
docker
bash