Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.
Sign up to join this community
I have a script I wrote in Bash that I'm trying to modify to be POSIX-compliant. I have managed to get everything working except I cannot get the EXIT trap to trigger when the process is terminated with killall, CTRL+C or closing the terminal - as it did with Bash. Here is my exit trap:
#!/bin/sh
TMP=$(mktemp /tmp/countdown.XXXXX)
trap 'rm -rf $TMP' EXIT
In a strictly POSIX shell, the EXIT trap is evaluated before the shell exits due to executing exit or due to executing the last command in a script. It is not executed if the shell exits due to a signal.
Would you want to catch Ctrl+C, you would have to trap INT (the "interrupt" signal). If closing the terminal sends the script a HUP ("hang-up") signal, you would have to trap that too.
trap 'rm -rf "$TMP"; trap - EXIT; exit' EXIT INT HUP
You may also want to trap TERM, the generic "terminate" signal sent by default by kill.
The trap above explicitly resets the EXIT trap so that it's not called again when the script exits due to receiving one of the listed signals.
exit in a SIGINT trap: unix.stackexchange.com/search?q=wait+and+cooperative+exit
dash.
kill utility can be used to test what signals the shell understands: dash -c 'kill -l'. I have personally never heard of a POLL signal.
Just remove the temporary file immediately after creating it, and read & write to it via a file descriptor.
Pass it as /dev/fd/[fd] or /proc/self/fd/[fd] to commands which expect a path.
Example:
t=$(mktemp); exec 5<>"$t"; rm "$t"
echo some text >&5
exec 5<>/dev/fd/5 # rewind / seek back at the start of the file
cat <&5
cmd1 /dev/fd/5 # cmd1 only takes paths
cmd2 5>&- # don't leak fd 5 to cmd2
You can also open the tempfile as multiple separate fds, as in exec 5<"$t" 6>"$t".
The rewind trick is linux-only; I cannot think of any portable way of doing it; ideas are welcome ;-\
