Hi Scott,
this is wrong: One of the improvements of GRASS 4.2.1/4.3/5.0 have
been that GRASS uses up to 24bit.
Then I guess I can change it back. The problem thre was that I was
reading old documentation that probably didn't have anything past
4.0/4.1.
But the problem you have may be related to the "locks" directory.
Please see the FAQ for it.Best wishes
Markus
Okay, here's the setup for when GRASS is not running is is running with
no monitor started.
cc999683-a /opt/grass/locks> ls -a *
cc999683-a:
. ..
cc999683-a.my.net.service.com:
. ..
And after I run `d.mon -s start=x0'
cc999683-a grass/locks> ls -a *
cc999683-a:
. .. mon.5475
cc999683-a.wlgrv1.pa.home.com:
. ..
I also have a symlink from /usr/local/grass4.3 to /opt/grass.
After that, I try `d.mon select=x0' at which point GRASS just locks up.
I tried looking at the FAQ, but I cannot find instructions to do
anything that I have not done yet as it only mentions the locks and I
can't discern any difference between what it says and how I have it
installed.
Scott Smith