starting mex?

[Brent Bates ViGYAN AAD/TAB]

   We have 3130 and I always use Mex when I log on the console.  I don't know
of anything special you have to do.  Below is a clip from my .login:

ismex
if( $status == 0 && `tty` == '/dev/console' ) then
   mex
   clock
   gsh -f small7 -s 66 80
endif

   This checks to see if mex is already running and if it isn't then it is
started.  Using gsh on a 3130 is better than using the Mex menu option to
open a new window, gsh is about half way between the Mex new window and wsh
on a 4D.  Below is a clip from my .logout, this is VERY important:

ismex
if($status == 1 && `tty` == '/dev/console') then
   kill -9 `ps x | grep 'clock$' | awk '{print $1}' `
   kill -9 `ps x | grep 'w[0-9]' | grep 'csh (csh)' | awk '{print $1}' `
   kill -9 `ps ax | grep 'gsh' | grep -v 'grep' | awk '{print $1}' `
   kill -9 `ps x | grep 'mex$' | awk '{print $1}' `
endif

   You MUST kill ALL windows BEFORE exiting mex or the system gets screwed
up and the only way to clear it is to reboot, but reboot in a NORMAL fashion,
as in: sync;sync;reboot  as root.
   I have also seen problems when root uses mex.  If root uses mex and opens
some windows, other users will not be able to open windows.  Below is my
.logout for root to correct this problem:

ismex
if($status == 1 && `tty` == '/dev/console') then
   kill -9 `ps x | grep 'clock$' | awk '{print $1}' `
   kill -9 `ps x | grep 'w[0-9]' | grep 'csh (csh)' | awk '{print $1}' `
   kill -9 `ps ax | grep 'gsh' | grep -v 'grep' | awk '{print $1}' `
   kill -9 `ps x | grep 'mex$' | awk '{print $1}' `
   chmod a+rw /dev/ttyw*
endif

   The important difference here is the chmod.
   I hope this is of some help.  Good luck. (you'll need it)

	Brent L. Bates
	NASA-Langley Research Center
	M.S. 361
	Hampton, Virginia  23665-5225
	(804) 864-2854
	E-mail: blbates at aero36.larc.nasa.gov or blbates at aero8.larc.nasa.gov