[GRASSLIST:3931] Re: Can't start monitor

[Glynn Clements]

Helmer Schack-Kirchner wrote:

> We have successfully compiled and installed Grass5.0.0pre4 on linux
> (SUSE8.0), however the <d.mon start=x0> command produces the following
> error code:
> "Could not execute monitor: No such file or directory.

This means that mon.start failed to execute the driver as specified in
$GISBASE/etc/monitorcap, which should be $GISBASE/driver/XDRIVER.

Either:

a) XDRIVER failed to compile (look for $GISBASE/driver/XDRIVER; if it
isn't there check error.log and the output from "make" for the
reasons), or

b) $GISBASE/etc/monitorcap is broken; the entry for "x0" should look
like this:

	x0:driver/XDRIVER:X-windows graphics display: \
	     dev/fifo.1a dev/fifo.1b \
	     ::any terminal

[Note: $GISBASE is the top level directory of the GRASS installation,
which is /usr/local/grass5 unless you put it somewhere else using
configure's --prefix option.]

> No socket to
> connect for monitor <x0>. Will try once more. No socket to connect to
> for monitor <x0>."

The subsequent error messages are a consequence of the fact that the
monitor isn't running.

> (This problem has yet been reported as [GRASSLIST:2839] Re: d.mon can't
> bind to socket ), however, the answers did not help us:

This is not the same problem as reported in GRASSLIST:2839. In that
case, the driver was running, but the client couldn't connect. In your
case, the driver isn't running.

-- 
Glynn Clements <glynn.clements at virgin.net>