Prevent SIGINT from interrupting function call and child process(es) within
Consider the following script:
signals
When typing ctrl-c in a terminal, why isn’t the foreground job terminated until it completes?
If Bash is waiting for a command to complete and receives a signal for
which a trap has been set, the trap will not be executed until the
command completes.
How to signal the end of stdin input
In Bash, I learned that the ending signal can be changed by here document. But by default how can I signal the end of stdin input? I happened to find that with cat and chardet, their stdin inputs can be signaled as finished by Ctrl+D. But I seems to remember that Ctrl+D and Ctrl+C are … Read more
Why does SIGUSR1 cause process to be terminated?
I was surprised with this comment in other question:
Why can’t I kill a SIGSTOP’d process with a SIGTERM, and where is the pending signal stored?
I am using Debian stretch (systemd).
I was running the rsyslog daemon in foreground using
/usr/sbin/rsyslogd -n
and I did a Ctrl+Z to stop it.
The state of the process changed to Tl (stopped, threaded).
I issued multiple kill -15 <pid> commands to the process, and the state of the process was the same: Tl. Once I did an fg, it died. I have 3 questions.
What is signal 0 in a trap command?
I’m following this guide on how to set up passwordless SSH authentication with ssh-agent.
Control which process gets cancelled by Ctrl+C
I have a live CD that boots into Linux and runs a small Bash script. The script searches for and runs a second program (which is usually a compiled C++ binary).
Difference between less violent kill signal -HUP (1) -INT (2) and -TERM (15)
Apart from the most violent kill -9 (SIGKILL), I don’t quite understand the difference between the 3 other common signals (here) -HUP (1), -INT (2), and -TERM (15).
Ctrl+C does not work in gnome-terminal
On my Linux host, Ctrl+C does not seem to work and I do not know how to proceed to make it work. I am using Ubuntu 10.04 with bash 4.1.5(1), and working in Gnome-terminal.