POSIX says that "setting a trap for SIGKILL or SIGSTOP produces undefined result... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		arp242 on June 20, 2023 \| parent \| context \| favorite \| on: “Exit traps” can make your Bash scripts more robus... POSIX says that "setting a trap for SIGKILL or SIGSTOP produces undefined results", but for signals it describes SIGKILL as "Kill (cannot be caught or ignored)". I'm guessing this is some relic from 80s Unix systems where SIGKILL behaved different, or perhaps just an inconsistency/oversight.

nerdponx on June 20, 2023 [–]

I read that as undefined in terms of how the shell itself handles it, because the OS doesn't care.

remram on June 21, 2023 | [–]

I think it means that it is valid for OSes to return an error instead of doing nothing, if you attempt it.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact