unlocking monitor x0

[martijn at scanner.frw.uva.nl]

Hi Cliff,
	this is no direct answer to your question, but when we have 
problems with disobedient monitors that the normal GRass options can't 
solve, we do
	ps -ef|grep <monitorname>
and
	kill -9 <PID of monitor>
After that, a clean restart of the monitor is possible.
Hope this is of some use to you...

Martijn van Leusen

On Sun, 6 Mar 1994, Cliff Behrens wrote:

> Somehow, I seem to have lost the file containing current monitor status info.
> When I try to start x0, I am told it is already running.  When I use d.mon -L
> to check monitor status, I receive nothing back.  I have tried using the
> stop=x0 unlock=x0 options to free x0, but his doesn't work.  Where is the
> file that stores current info on monitor status?  Thanks for anybody's help
> on this one.
> 
> Cliff Behrens
> ============================================================================
> 
> Mapset <MORENET> in Location <layers> 
> GRASS 4.1 > d.mon start=x0 select=x0
> Graphics driver [x0] is already running
>  Problem selecting x0. Will try once more
> 
> Mapset <MORENET> in Location <layers> 
> GRASS 4.1 > d.mon stop=x0 unlock=x0
> Monitor 'x0' terminated
> 
> Mapset <MORENET> in Location <layers> 
> GRASS 4.1 > d.mon unlock=x0
> 
> Mapset <MORENET> in Location <layers> 
> GRASS 4.1 > d.mon -L
> name            description                    status
> ----            -----------                    ------
> 
> Mapset <MORENET> in Location <layers> 
> GRASS 4.1 > 
>