some questions about unix processes https://questions.wizardzines.com/unix-processes.html …
-
-
Replying to @b0rk
it's a really extreme level of "well actually", but you _can_ mmap a bunch of memory, write some code to it, mprotect it RX, map some space for a stack, then call clone() to start a new process running that code, without it ever having to exist as an executable on-disk
1 reply 0 retweets 5 likes -
(which is ultimately very similar to how a JIT works, just, those usually create threads within an existing process, or have existing threads jump into the generated code, rather than creating a whole new process to run it)
1 reply 0 retweets 2 likes -
also, SIGSTOP can't be blocked or have its handler overridden, just like SIGKILL
1 reply 0 retweets 1 like -
linux _can_ be configured not to expose /proc/X/cmdline to all users, but it's usually not so the advice is good regardless
1 reply 0 retweets 0 likes -
2 processes _can_ write to the same file at the same time, but the writes aren't guaranteed to be atomic; bytes from one write can interleave between bytes from another! It's important to use some sort of locking mechanism when this isn't acceptable (pipes have _some_ guarantees)
3 replies 0 retweets 1 like
There are some atomicity guarantees, though relying on that for anything other than the "multiple loggers to the same logfile" use case is a recipe for trouble. E.g. CephFS does not always guarantee it (and that's one of the very few ways it's not strictly POSIX compliant).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.