Rethinking race-free process signaling
Rethinking race-free process signaling
Posted Apr 6, 2019 20:05 UTC (Sat) by zlynx (guest, #2285)Parent article: Rethinking race-free process signaling
I have seen software broken by large PIDs. Arguably though they're just doing it wrong, especially in 2019.
There's no purpose in using "short" to store PIDs when we have "pid_t" and using "char[6]" as string storage for a PID has always been a pretty bad idea. The print formatting that assumes six columns is ugly but not dangerous, and apparently people just don't care, as "vmstat" has had broken column widths for at least ten years (block IO per second and memory sizes are much larger than vmstat originally designed for).