xevion/undefined.behavio.rs
1
0
Fork 0
mirror of https://github.com/Xevion/undefined.behavio.rs.git synced 2025-12-10 22:09:01 -06:00
Code Issues Packages Projects Releases Wiki Activity

Reformat race conditions post

Browse Source
This commit is contained in:
Xevion
2023-11-26 08:49:11 -06:00
parent cdfa3c3bf9
commit c777c132f6
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/content/blog/race-conditions-in-signal-handlers.md
View File

@@ -16,10 +16,9 @@ Signals are a special, but very primitive way for processes to communicate funct
a standardized interface available to 99.99% of programs run on UNIX systems (in existence). Interaction can be done
with just the `kill` command.
While the signals API can be quite bare bones and simple, it's technically much less complex compared to a network
interface, usage of STDIN/STDOUT, a file, or even a shared memory segment. These other options might have a lot more
features,
but none of them are perfectly standardized, completely secure, or simple to use.
While the signals API can be quite bare bones and simple, it's technically much less complex compared to a network interface, usage of `STDIN` & `STDOUT`, a file, or even a shared memory segment.
These other options might have a lot more features, but none of them are perfectly standardized, completely secure, or simple to use.
If you're looking to allow basic communication with your program for very specific use cases and don't need complexity
or I/O, signals can be a great way to go.