Skip to content
This repository was archived by the owner on Dec 29, 2024. It is now read-only.

Commit 9c6927a

Browse files
committed
Use underscore italic notation, remove unfinished sentence
1 parent 58a1b0e commit 9c6927a

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ there's a way to check whether signal handlers have been provided or a process.
113113

114114
On Unix systems (which is the only place you're going to find Unix signals), there's a special pseudo-filesystem that
115115
provides intimate details on a process. This includes things like the process's name, state, PID, memory usage, threads,
116-
and of course: *signal handlers*.
116+
and of course: _signal handlers_.
117117

118118
See below, the contents of `/proc/<pid>/status` for a process:
119119

@@ -178,8 +178,6 @@ If the result is non-zero, the bit is set. If the result is zero, the bit is not
178178

179179
By simply polling the process's signal handlers, we can wait for the signal handler to be registered before sending the `SIGUSR1` signal.
180180

181-
Signal handlers are typically registered quickly, and they're
182-
183181
### Credits
184182

185183
Credit to [Eryk Sun][python-discuss-solution] for explaining the issue and providing an immaculate solution to signal

0 commit comments

Comments
 (0)