[...]
> > PID TTY MAJFLT MINFLT TRS DRS SIZE SWAP RSS SHRD LIB DT
> COMMAND
> > 408 ? 12119 1585263 720 20492 36784 15572 21212 816 0
> 4921 X :0 -bpp
[...]
Look on the bright side! 5 megs of the process is swapped out... all you
have to worry about is running out of swap...
Maybe you could do the following. Assuming you startx from your profile,
what about doing:
# .profile
>~/.want-X-resume
while [ -f ~/.want-X-resume ]
do
startx
done
This creates a zero-length file in your home directory. As long as it
exists, every time you quit out of X it will automatically restart. To
kill X for good, you have to first delete ~/.want-X-resume . After
having done that you will really quit X. You could edit your window
manager to do this for the Quit choice.
The trick is then to detect when the machine has been idle for a good
while and all non-essential apps have been closed down (could be
non-trivial; depends on your setup), and then send X a signal to shut
itself down (or just use cron for a 3am kill). X will spring back again,
thanks to the .profile loop. That way you will release all leaks, a la
Apache.
All this is completely off the top of my head, but it seems like it
could work in theory.
DL
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
