mayday (m'aidez) our monitors are sick

GRASS GRASS user
1

Received: from SpoolDir by ROB (Mercury 1.13); Wed, 8 Mar 95 22:58:34 +0100
Return-path: <grass-lists-owner@moon.cecer.army.mil>
Received: from sol10 by hercules.archis.nl (Mercury 1.13);
    Wed, 8 Mar 95 22:58:25 +0100
Received: from ginko.cecer.army.mil by sol10 (5.0/SMI-SVR4)
    id AA04831; Thu, 9 Mar 1995 00:56:57 --200
Received: (from daemon@localhost) by ginko.cecer.army.mil (8.6.9/8.6.9) id NA

A06793 for grassu-people; Wed, 8 Mar 1995 13:06:10 -0600

Received: from max.cecer.army.mil (max.cecer.army.mil [129.229.20.254]) by gi

nko.cecer.army.mil (8.6.9/8.6.9) with ESMTP id NAA06790 for <grassu-list@ginko.
cecer.army.mil>; Wed, 8 Mar 1995 13:06:08

0600
Received: from hermes.aston.ac.uk (hermes.aston.ac.uk [134.151.79.46]) by max

.cecer.army.mil (8.6.9/8.6.9) with ESMTP id NAA05798 for <grassu-list@max.cecer
.army.mil>; Wed, 8 Mar 1995 13:00:56 -0600

Received: from sun.aston.ac.uk (actually host hawaii.aston.ac.uk)
          by hermes.aston.ac.uk with SMTP (PP); Wed, 8 Mar 1995 19:05:16 +000

0

From: charnotw <charnotw@helios.aston.ac.uk>
Date: Wed, 8 Mar 1995 19:03:49 GMT
Message-Id: <13343.9503081903@sun.aston.ac.uk>
Sender: grass-lists-owner@moon.cecer.army.mil
Reply-To: grassu-list@moon.cecer.army.mil
Precedence: Bulk
To: grassu-list@max.cecer.army.mil
Subject: mayday (m'aidez) our monitors are sick
X-Sun-Charset: US-ASCII
Content-Length: 1229
X-PMFLAGS: 33554560

We have an epidemic of monitors failing.

basically they lock up and become totally unresponsive
even if you completely logout and start up GRASS again
you just get the message:

GRASS 4.1 > d.mon start=x0
Graphics driver [x0] is already running
Warning - no response from graphics monitor <x0>.
Check to see if the mouse is still active.
ERROR - no response from graphics monitor <x0>.
Problem selecting x0. Will try once more
Warning - no response from graphics monitor <x0>.
Check to see if the mouse is still active.
ERROR - no response from graphics monitor <x0>.

Mapset <watertables> in Location <shropshire>
GRASS 4.1 >

stopping them produces a response:

GRASS 4.1 > d.mon stop=x0
Monitor 'x0' terminated

Mapset <watertables> in Location <shropshire>
GRASS 4.1 >

but they can still not be started (same message as above)
I've only lost the use of x0 but other people have lost
x1 and x2 (we'll run out soon!.
We have been using GRASS for ages and this has only just
started, anybody got any bright ideas?

cheers Tom :sunglasses:

Tom Charnock O--O
Dept Civil Engineering (~~~~)
Aston University ( __ )
Birmingham B4 7ET UK /|\ /|\
charnotw@sun.aston.ac.uk

I presume you are running the message queue version of the
grass monitor. I you do, you can use the following script

********* begin *********

:
NAAM=$1
if [ "$NAAM" = "" ]
then
    echo "Usage: KillX username"
    exit
fi
eval `ipcs -aq | awk '{if ( $5 == NAAM ) print "PID=" $13 }'
NAAM=$NAAM`
for P in `ps -e | awk '{if ( $4 == "XDRIVER" && $1 == PID) print $1}'
PID=$PID`
do
    kill -9 $P
done
for i in `ipcs -aq | awk '{if ($1 == "q" && $5 == NAAM) print $2}'
NAAM=$NAAM`
do
    ipcrm -q $i
done
******end*******

The problem with these MQ's is that the Xdriver keeps running when
it's out of sinc. the script kills the Xdriver, and -very important-
removes the MQ's. You have to run the script (as user root) for each
user that has a hanging Xdriver. You can check wether your system
uses MQ's by running the program:

ipcs -aq

See the man page for ipcs.

Succes

Ronald Wiemer