On 13-11-10 05:24 AM, Andrej N. Gritsenko wrote:
>      In fact, auto-restart might be needed only if some component crashes.
> And also in fact, in many cases this does not work at all, because when
> that happens, the possibility that conditions for the crash still present
> is high so it crashes again and again. I'm not sure if auto-restart have
> to be there at all.

Auto-restart is very important to have for core desktop components and 
it's also very nice to have as an option for other things which can die 
as a result of transient error conditions.

For example, if Openbox and LXPanel didn't auto-restart, I'd be forced 
to patch their desktop files to launch this sort of thing instead.

sh -c 'until lxpanel --profile Lubuntu; do echo; done'

(The most concise way I've found to say "Restart until it exits cleanly" 
but still an annoying source of pointless clutter in process lists.)

I actually DO use that for conky because it likes to randomly die on me 
after several days of runtime and I didn't have the time to figure out 
how to opt-in for auto-restart when I set it up and I still don't have 
time to fiddle around with enabling core dumping at the moment.

Other examples of persistent but transient crash-causing conditions 
where auto-restart has saved me tons of frustration:

- Fiddling with PDF viewer windows has sometimes caused Openbox to crash 
persistently but somewhat unpredictably. Thanks to auto-restart, all my 
windows flicker and then I can get back to work.

- Rapidly opening and closing LibreOffice windows as part of splitting a 
.DOC into several dozen per-chapter HTML files can cause LXPanel to 
freeze or crash.

   In the former case (lxpanel freezes), I hit Win+Space to pull up
   gmrun (habit since I normally demand a run dialog with tab completion
   and command history) and type "killall -SEGV lxpanel" because it's
   easier than remembering or looking up the exact command to respawn it
   after SIGTERM causes lxsession to omit the auto-restart.

   In both cases (freeze or crash), I then usually have to hit Win+Space
   again and type "sh -c 'audtool shutdown; sleep 2; audacious &'"
   because LXPanel is the only panel which doesn't take responsibility
   for recovering tray icons and Audacious is one of a handful of apps
   (Audacious, neap, oDesk Team) which don't take responsibility for
   re-creating their tray icons and, since no Audacious devs use LXDE,
   their response is "Unless you want to provide a patch, it's a bug in
   LXPanel, not Audacious, since it works in Xfce, GNOME, KDE, etc."

- Various PCManFM crashes I've encountered over the years.

Plus, it's a lot easier to tell my mother to "killall <...>" over the 
phone than it is to talk her through dropping into the system console, 
setting DISPLAY, and re-launching openbox with the correct profile 
specified because, when the window manager dies in a DE, a non-wizard is 
essentially in a "You need a terminal to launch the WM. You need the WM 
to launch and focus a terminal." situation.


------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list

Reply via email to