New answers tagged signals
Without -h the job is removed from the table of active jobs, with -h it is not. Everything is in the manual: disown [-ar] [-h] [jobspec ...] (...) If the -h option is given, each jobspec is not removed from the table, but is marked so that SIGHUP is not sent to the job if the shell receives a SIGHUP. To see the ...
Some machines have short run batteries designed for just shutdown (AT&T 3B series did, at least, and IIRC some IBM RS/6000-pSeries did too). In these machines, the SIGPWR signal was sent on power loss and was actually useable. Not so much these days.
The problem is well explained here, as WCE wait and cooperative exit and I encourage you to read it. Basically, your signal is received by all foreground processes, ie the shell and the program, sleep or aplay. The program exits with return code 130 if it does not handle the signal. The shell does a wait for the child to end, and sees this, and the fact that ...
you could try this, i had this issue a few times and idk why this worked by it did. $(sigint) this is to dislay the result like a var is bash, but to do so it has to run it and some times works.
Top 50 recent answers are included