View Single Post
Old 09-29-2013, 08:28 AM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
stop lab126_gui stops the UI, and still leaves X running (which you'd stop by, you guessed it stop x).

If you kill x, start x restarts everything. If you don't, start lab126_gui.

(Why lab126_gui and not framework? Because it's a meta event, and handles a bunch of other things more neatly (the progress bar, among other things)).

You will have to trap SIGTERM if this is used in a KUAL script, because stopping the framework propagates a SIGTERM to everything the framework launched (meaning KUAL & the script it ran). Check the ScreenSavers/Fonts KUAL extension for examples of how I did it for X or the framework (because busybox's trap implementation is finicky, and so is upstart, so you can potentially confuse upstart by doing it wrong).

Last edited by NiLuJe; 09-29-2013 at 11:08 AM.
NiLuJe is offline   Reply With Quote