xevion/v2.xevion.dev
1
0
Fork 0
mirror of https://github.com/Xevion/v2.xevion.dev.git synced 2025-12-05 23:16:47 -06:00
Code Issues Packages Projects Releases Wiki Activity

Use underscore italic notation, remove unfinished sentence

Browse Source
This commit is contained in:
Xevion
2023-11-02 13:22:37 -07:00
parent 58a1b0e9b4
commit 9c6927a99f
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
_posts/2023-07-26-race-conditions-in-signal-handlers.md
View File

@@ -113,7 +113,7 @@ there's a way to check whether signal handlers have been provided or a process.
On Unix systems (which is the only place you're going to find Unix signals), there's a special pseudo-filesystem that
provides intimate details on a process. This includes things like the process's name, state, PID, memory usage, threads,
and of course: *signal handlers*.
and of course: _signal handlers_.
See below, the contents of `/proc/<pid>/status` for a process:
@@ -178,8 +178,6 @@ If the result is non-zero, the bit is set. If the result is zero, the bit is not
By simply polling the process's signal handlers, we can wait for the signal handler to be registered before sending the `SIGUSR1` signal.
Signal handlers are typically registered quickly, and they're
### Credits
Credit to [Eryk Sun][python-discuss-solution] for explaining the issue and providing an immaculate solution to signal