Grass4 d.mon problem under Debian 2.1

[Adalberto da Silva]

Markus,

my Linux machine is named 'debian' as long as it is a standalone station and
I didn't realise a better name for it. Then it's the default from Debian
install.

The lock dir is OK and when d.mon freezes it does write a lock file in it.
In other words, there is a lock file for the display but there is no
display.

I think the name of the lock dir is OK too because under debian 1.3 my
machine was the same with the same name, and it worked for me (and very
well, I must say).

Now, with Debian 2, everything works well with Grass 5, it has a lock dir
named 'debian' and it works.

As far as I can see, the problem is with Grass 4 *and* Debian 2 but I can
see no clue for this behaviour.
For my tests, it seems there's no connection with locks dir or Grass
installation itself. I think there's some trick on the way debian manages
the display, but what?

The most intriguing for me is the fact that Grass 5 is working (and it's
working fine) on the same machine under a different dir tree, using the same
name for lock dir; better saying: everything is the same for Grass 5 or
Grass 4, except for the locations of the binaries, and only one has a fully
working display for d.mon.

Thanks in advance,

Adalberto