If I begin a process and background it in a terminal window (say ping google.com &), I can kill it using kill %1 (assuming it is job 1).
However if I open another terminal window (or tab) the backgrounded process is not listed under jobs and cannot be killed directly using kill.
From what I understand, SIGKILL cannot be caught. This would imply that a process does not have time to kill it's children before the OS destroys it. This can be demonstrated with a shell script.
#!
I want to change default terminal to lilyterm. Here is instructions that I've found on the internet
gsettings set org.gnome.desktop.default-applications.terminal exec lilyterm
gsettings set org.gnome.desktop.default-applications.terminal exec-arg ""
But when I'm pressing shotcut, that must run default termial -- I'm getting
Windows manager warning: Error on terminal command"(null)".
I'm trying to launch one command in a new gnome-terminal window from a shell script, and it seems that my .bashrc file doesn't get sourced when calling gnome-terminal and executing a command:
gnome-terminal -t "my title" -e vim
But it does when launching gnome-terminal alone:
gnome-terminal -t "my title"
(for testing purposes, just add a echo "something" to the end of the .bashrc)
I also tr
I am running Fedora 17 gnome (shell) 3 and gnome terminal 3.4.1.1.
I am a user of both gnome-terminal and midnight commander. As default gnome-terminal has always used F10 (which I need while using mc), to opening the top menu. So was this time.
I have a program which is supposed to handle SIGINT and gracefully shut down. When I run this program from a terminal without backgrounding it I can shut it down just fine using Ctrl-C. Inspecting the logs shows that everything worked as expected.
When I open a separate terminal and call kill -2 [pid] or kill -s INT [pid] it does nothing.
I was explaining to a friend that the graphical interface in Linux is a separate program that can be killed like any other. To demonstrate that I switched to tty1 and tried to kill the GUI (as a real-life scenario of when the GUI freezes or crashes).
how to run a run a shell script in background even if i exit the terminal or logout,
the process end only when i kill with command kill
How do you send a lost signal with the kill process command?
I have tried all of them I thought but still cannot figure this out. Any help is greatly appreciated.
To send signals to the program, launch another terminal window and
enter the command kill -3 1111 where 1111 is replaced with the
process ID reported by sigCatch. What does sigCatch report?