John Siracusa on Nostr: I went so far as to write a “native” package for Node.js that lets me call ...
I went so far as to write a “native” package for Node.js that lets me call sigprocmask() to block SIGUSR2 only to find that apparently it…does nothing? The call succeeds (i.e., returns 0) and all the arguments look correct, but the supposedly blocked signal still gets through.
Has anyone out there successfully blocked a signal in Node.js? I mean actually block, not just use process.on(…) to add a no-op handler function.
Published at
2024-11-26 18:15:00Event JSON
{
"id": "cf1c3f1ba18f3082ee0d7723b7c9fc1d97b2ebcabfd06f3a0975e60d904848ae",
"pubkey": "f83dfad0f8d080042fb53d1c883ab96b5c11a61b174dca15d050a64c61b7287b",
"created_at": 1732644900,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/siracusa/statuses/113550616209446340",
"activitypub"
]
],
"content": "I went so far as to write a “native” package for Node.js that lets me call sigprocmask() to block SIGUSR2 only to find that apparently it…does nothing? The call succeeds (i.e., returns 0) and all the arguments look correct, but the supposedly blocked signal still gets through.\n\nHas anyone out there successfully blocked a signal in Node.js? I mean actually block, not just use process.on(…) to add a no-op handler function.",
"sig": "1b7d92f89af15302e08b6d7526227102265bc917140cb8e35f56836c8a08b1e0b2c4674ff5260037a81f345afcf2cea3fd0a932503fbc0af7c7aaf131eeba1b2"
}
