diff --git a/_posts/2023-07-26-race-conditions-in-signal-handlers.md b/_posts/2023-07-26-race-conditions-in-signal-handlers.md index 5ccb790..894d682 100644 --- a/_posts/2023-07-26-race-conditions-in-signal-handlers.md +++ b/_posts/2023-07-26-race-conditions-in-signal-handlers.md @@ -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//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