signals

I have a program which takes a long time to complete. I would like it to be able to catch SIGINT (ctrl-c) and call the self.save_work() method. As it stands, my signal_hander() does not work since self is not defined by the time the program reaches signal_handler() . How can I set it up so self.save_work gets called after a SIGINT ? #!/usr/bin/env python import signal def signal_handler(signal, frame): self.save_work() # Does not work exit(1) signal.signal(signal.SIGINT, signal_handler) class Main(object): def do_stuff(self): ... def save_work(self): ... def __init__(self): self.do_stuff()

I have a python script and it will loop through bunch of maya files and do some stuff. But some time maya get seg fault and my script will stop there. I tried with signal and multiprocess. But both failed import os, optparse, glob, json, signal import maya.standalone import maya.cmds as cmds from multiprocessing import Process, Queue def loadMayaBd(): maya.standalone.initialize(name='python') def sig_handler(signum, frame): print "segfault" def doSome(args, options): signal.signal(signal.SIGSEGV, sig_handler) loadMayaBd() #from here its just a example fileNameList = args[0] for eachFile in

I read the man page of a signal using man 7 signal where I see two types of signal. So, I have question, What is the difference between POSIX reliable signals and POSIX real-time signals in Linux? These days, it might be better to phrase these as ordinary signal semantics versus realtime signal semantics. In some early UNIX systems, signals were unreliable in that they could be "lost", because there was no facility to block signals (to keep them pending). For example, code about to call pause() after checking a wake_up_flag set by a signal handler might miss the wake up instruction if the

I frequently use the sendsignal tool for WebSphere Application Server processes (server, launchClient, wsadmin, etc.) in order to generate heap dumps. However, sendsignal doesn't work on 64-bit machines. Does anyone know of an alternative for sending the ctrl-break to a remote process? Update: Bengt points out that this is basically the same as the following question. So, I guess my question is: has anyone found a way around this limitation in the past two years? Can I send a ctrl-C (SIGINT) to an application on Windows? Why use a control break for the dumps why not use the commands that are

On a happy (if not irrevelent) note, this is the absolute last obstacle in this particular project. If I fix this, I have my first significant dot release (1.0), and the project will be going public. Thanks to everyone here on SO for helping me through this project, and my other two (the answers help across the board, as they should). Now, to the actual question... I have a toolbar in my application (Python 2.7, PyGTK) which has a number of gtk.ToolButton objects on it. These function just fine. I have working "clicked" events tied to them. However, I need to also connect them to "enter-notify

My questions are: Is there a way to conclusively determine if a function is async-signal-safe if you don't have access to its implementation? If not, is there a way to test if function would be async-signal-safe enough to call from a signal handler? If you reads the man pages of signal() or sigaction(), you get a list of async-signal-safe functions (functions that can be safely called inside a signal handler). However, I believe that this list is not exhaustive. For example, the following page http://linux.die.net/man/7/signal , under the Async-signal-safe functions header, reads: POSIX.1-2004