On Mon, 25 Apr 2005 15:13:24 -0500 Patrick Bogen <[EMAIL PROTECTED]> wrote: > Oh, yeah, forgot to mention: if it does use SIGKILL, you're out of > luck as far as just intercepting the signal is concerned, since > SIGKILL isn't allowed to be stopped- but by that same token, it's not > supposed to be used as the first try at killing a process. Anyway, the > idea of a script to clean up and kill blackbox instead of just exiting > sounds like it might be the best option- this might be something worth > incorporating into the main sources. Perhaps a "Shutdown" option as > opposed to just "Exit"; killing blackbox to end the X session is > probably a fairly common operation- I suppose the question is, can we > consider sending a term/hup signal as part of blackbox's purpose of > "managing windows"?
I'm not sure about that. AFAIK, X was designed around a "watched" application, whose termination tells X to stop. I'm not even sure if X actually kills apps itself or them dying is part of the x libs, as a reaction to X being dead. Perhaps there's some options about this in the X man pages? Returning to Dave's problem: basically you need Sylpheed to die nicely, right? I had the same issue when I pressed the power button; acpid intercepts that and runs a script. That script would run poweroff directly. I've inserted the following to allow Sylpheed to die nicely: killall sylpheed && sleep 1 Instead of running blackbox directly from your .xinitrc, run a script such as this: exec myscript.sh and myscript.sh being: #!/bin/sh blackbox killall sylpheed && sleep 1 -- Ciprian Popovici -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] List archives: http://asgardsrealm.net/lurker/splash/index.html
