06-01-2012
Thanks for the answer, but to do that i do not even need to quit to another session do I? I can put process in the background and kill it afterwards. What I mean is find the way how to kill the script ASAP.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I ask this question since sometimes i run a time-consuming ftp in foreground and forget to use nohup ftp.sh & to put this work background and can still running after i log off.
Assume this ftp task have run 1 hour, and still 1 hour time to end,
i don't want to abort the ftp, first, i use ctrl+Z... (3 Replies)
Discussion started by: stevensxiao
3 Replies
2. Shell Programming and Scripting
Does anyone know how to program signals in fmli?
My fmli script goes in loop when the telnet session is closed. When I start the script from the prompt the issue do not happen. But when it is started by the login process it hags. That's why I want to program the SIGHUP to exit/finish the script.... (0 Replies)
Discussion started by: Marcos Brito
0 Replies
3. Programming
Hi,
Recently I was reading some c coding by some colleagues and I noticed that the above trend. They will create a pipe for the process then they will use the standard signal handler to capture a particular signal and write that signal to the pipe. On the other end, the process will read the... (7 Replies)
Discussion started by: joseph_ng
7 Replies
4. Shell Programming and Scripting
hey champs,
I have a process running.......i have to catch/trap the signal when the process is being interupted/killed (kill -9 pid) option......
how can i achieve the same thru my process........
let my process is a.sh and it supposed to take 13 mins to complete, but due to some problem ,... (15 Replies)
Discussion started by: manas_ranjan
15 Replies
5. Shell Programming and Scripting
hi ,
What is the trap signal for "ENTER key"? (4 Replies)
Discussion started by: Sreejith_VK
4 Replies
6. Programming
i am creating children processes using fork system call
every child i create goes to sleep for random time.
when child stops running how can i catch his signal and turminate the child (2 Replies)
Discussion started by: emil2006
2 Replies
7. UNIX for Dummies Questions & Answers
hi all ,
I want to execute a script on the user logout(using gnome environment).
Is ther any way to execute it through TRAP stmt? (2 Replies)
Discussion started by: harsha10
2 Replies
8. Programming
Hi!
I want to catch all signals that my program receives print their name and then execute the default handler.
Can you help me on that?
I've tried the following code:
#include <stdio.h>
#include <unistd.h>
#include <signal.h>
void (*hnd)(int i);
char signals =
{
"SIGHUP",... (7 Replies)
Discussion started by: dark_knight
7 Replies
9. Shell Programming and Scripting
I just want to trap kill -9 signal issued by any of user from any terminal and just capture that user terminal who had raised this kill -9 command (1 Reply)
Discussion started by: puneet.goel
1 Replies
10. Shell Programming and Scripting
Hello all!
I'm writing a script that will catch when an outside process crashes (SIGHUP, right?) without having to loop into infinity.
With that in mind, I came across the trap utility and thought if could be used to monitor another process other than it's own. But from what I've read, I'm... (1 Reply)
Discussion started by: mashiox
1 Replies
LEARN ABOUT SUSE
gnome-session-save
GNOME-SESSION-SAVE(1) General Commands Manual GNOME-SESSION-SAVE(1)
NAME
gnome-session-save - Saves or ends the current GNOME session
SYNOPSIS
gnome-session-save [--logout] [--force-logout] [--logout-dialog] [--shutdown-dialog] [--gui] [--kill [--silent]]
DESCRIPTION
gnome-session-save can be used from a GNOME session to save a snapshot of the currently running applications. This session will be later
restored at your next GNOME session.
The --gui option will report errors in dialog boxes instead of printing to stderr.
If called with the --logout option, the current GNOME session will be ended, unless logging out has been inhibited by an application. The
--force-logout option can be used to end the session regardless of the inhibition state.
When the --logout-dialog option is given, the standard dialog displaying logout options is displayed. When --shutdown-dialog option is
given, the standard dialog displaying shutdown options is displayed.
The --kill and --silent options are deprecated. The --kill option is equivalent to the --logout-dialog option. If --silent is used with
--kill, then it will behave as if --logout was used.
The session is not saved when gnome-session-save is called with any of the options ending the session.
SEE ALSO
gnome-session(1)
BUGS
If you find bugs in the gnome-session-save program, please report these on http://bugzilla.gnome.org.
GNOME GNOME-SESSION-SAVE(1)