l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jun 28 16:42

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Part Way Into X
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Part Way Into X

On Fri, 28 Jun 2002, Peter Jay Salzman wrote:
> begin ME <dugan@passwall.com> 
> > These would likely be options or packages. I do not use RedHat, but might
> > expect it could come up like this... 
> > You choose to install a new game, and while doing so the installer tells
> > you that you need to install other packages. These other packages might
> > include names like those above ("add support for DRI", "Support for GLX",
> > "support for hardware accelleration", "3d video card support").
> mike, you prolly saw this in my previous post, but his card doesn't
> support DRI.  his mtrr's also weren't set up correctly.  but neither of
> these should be "problems".   
> i couldn't see anything obviously wrong with stderrput of startx.

Yeah, one of those "composing a message so cant read while
writing" things.

> jim, if you send me the output of dmesg, i'll look at your boot messages
> and see if anything is wrong there.
> the only reason why i suggest this is you mentioned that the machine's
> lost networking at the same time as it lost a functioning window/desk
> manager.
> sounds suspicious that both happened at the same time.  makes me think
> there might be a larger issue here.
> hmm...  just for shits and giggles, why not post the output of "df -h"?

It also might be a good idea to make startx into a wrapper that:
checks to see if ~/.X.log exists, and if so, moves it to ~/.X.log.0 and
then runs the "real" startx with a > ~/.X.log 2>&1 &

This way, if/when it happens again, you should be able to find the errors
where is died if they were actually logged.

The problem with this is that there is no guarantee that there was a sync
just before a freeze and the last bits of data may not actually be in the
log file. It is however, better than nothing.

You may also want to examine your distro to see if it has this feature
built-in. (That is to roll your X server output into different logs for
each restarts of the X Server.)

Below is a poorly designed wrapper that could be much better, but provides
with some very basic and not so secure code. (This is not production, it
is for one user doing a test on their own machine.)

You could mv the real "startx" to /usr/local/bin/startx and then save this
one where the original "startx" was and change the line below
"/path/to/real/startx" to "/usr/local/bin/startx" and then chmod 755 this
wrapper/shell script.

Once done, the next time you have this sort of problem... see if you can
find a way to get back to a shell and sync or just wait some time and hope
data does get synced or have a process sync often, or run a service to
allow sync to take place upon connect or try to enable synchronous writed
(costly) on your fs or...

Anyway, here is a basic wrapper that could be imporved in many places...
----- cut below this line such that the next line it in top of file ----
# new startx shell script and wrapper

#If there exists a file in the calling user's home directory called
#  ".X.log" ...
if [ -e ~/.X.log ]; then
	# Rotate the file to an archive: (only keep one for now)
	mv ~/.X.log ~/.X.log
	# If the exit status of the last command (mv) is non-zero
	#  (unhappy) ...
	if [ "$?" != "0" ]; then
		/bin/echo "Error with backing up last log file."
		/bin/echo "Rotated X Server Log file"
# If there is no file called ".X.log" in the caling user's home dir...
	/bin/echo "First instance of ~/.X.log - creating a new one"

#Tell the user what we do:
/bin/echo "Now starting X with stdout and stderr directed to ~/.X.log"
#Actually launch the real startx after it was moved/renamed and
# redirect stderr to std out and send std out to destructively
# overwrite the file ".X.log" in the calling users home dir and then wait
# for it to finish before moving on...
/path/to/real/startx $@ > ~/.X.log 2>&1
# Check the exit status. Of course, if X is really hosed, it will never
#  get here. However, on the off chance it is able to get here when
#  nothing else works, then sync the disk, etc.

export XEXITST="$?"

if [ "$XEXITST" != "0" ]; then
	/bin/echo "X Server exited with zero (happy) exit status.)

#Have this script return the same exit status of the real startx
exit $EXITST

----- cut above this line such that the prev line it in top of file ----

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.