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

Small post reformat

Browse Source
This commit is contained in:
Xevion
2023-11-27 16:47:05 -06:00
parent 02e2c44247
commit 884638091c
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -40,8 +40,8 @@ in my language of choice that maintained the speed of `tar`. But looking into th
specific, designated signals to [emit progress information][checking-tar-progress] for both archival and extraction
operations.
By starting `tar` with the `--totals` flag, it would emit a statistic when the operation completes. But to request
information during the operation, a signal must be chosen, like so `tar -x -f archive.tar --totals=SIGUSR1`.
By starting `tar` with the `--totals` flag, it would emit statistics upon completion. But to request
information during the operation, a signal must be chosen, like so: `tar -x -f archive.tar --totals=SIGUSR1`.
Emitting a signal can be done with the `kill` command, like so: `kill -USR1 <pid>`. This will send the `USR1` signal
to the process with the given PID. The `USR1` signal is a user-defined signal, and is not used by the system.