How to close X after application exits?

[Medox]

I have a script that starts Xvesa and right after it starts another application that needs X... but when I close that application, X remains loaded. I want to close it right after.

 

[robc]

something like this may work with the .xsession file (this is untested):

Code: [Select]

Xvesa -br -mouse /dev/psaux,5 -screen 1024x768x32 -shadow -nolisten tcp -I 2>&1 > /dev/null &
waitforX
/your/X/application
sudo killall Xvesa If you do not background your application in .xsession then when it closes all instances of Xvesa will be killed.

Or a script like this that is called by crond (limited to every 1 minute):

Code: [Select]

#!/bin/sh
if [ -z `pidof /your/X/application` ]; then
  sudo killall Xvesa;
fi

[mikshaw]

I think the method of running X in TC is maybe necessarily more complicated for this particular type of use because it means making things much simpler and lighter for the typical use.  In other distros I've accomplished what you want to do simply by switching the window manager with the desired application...after the app is closed X is closed.  With TC you must explicitly close X because it uses a very basic startx script that doesn't call xinit like the fatter distros do.

[Medox]

something like this may work with the .xsession file (this is untested):

Code: [Select]

Xvesa -br -mouse /dev/psaux,5 -screen 1024x768x32 -shadow -nolisten tcp -I 2>&1 > /dev/null &
waitforX
/your/X/application
sudo killall Xvesa

Thanks! This is exactly what I was searching for.

Btw, is there a difference between -screen ....... and -mode 0x...... ?

[Medox]

new problem... after i kill x, the menu that shows up isn't correctly positioned.
i mean, i've added a simple menu that should appear after exiting x but the first two or three lines (on top) dissapear.

"clear" nor "reset", placed in the menu or xsession (before the menu) position the upcoming menu correct 
i've even tried this: http://aplawrence.com/Bofcusm/542.html, but nothing... or i don't know the equivalent for TC (?)

this happens on two of my 3 pc's... those two aren't really the quickest but shouldn't get such problems (AMD 1800+ and a Pentium 3 with 500mhz)... on my dual core laptop everything works fine...