[GRASS5] GRASS 5 and sockets: default?

[Markus Neteler]

On Tue, Feb 20, 2001 at 08:26:27AM -0800, Eric G. Miller wrote:
> On Tue, Feb 20, 2001 at 05:05:04PM +0700, Justin Hickey wrote:
> > Hi
> > 
> > Markus Neteler wrote:
> > > the sockets driver is maturing quickly. Question is if
> > > we should make it default for the forthcoming 5.0.0
> > > or not.
> > > 
> > >  - we need a platform report about it's quality
> > >      o SGI:
> > 
> > The windows now close when using tcltkgrass, but I get e-mailed the
> > message 
> > 
> > GIS ERROR: Monitor <x0> is already running
> > 
> > I'm not sure why.
> 
> Well, for some reason I see tcltkgrass has a "d.mon start=$mon" followed
> by a "d.mon stop=$mon".  I'm not sure why it's set-up like this...
> 
> In src/tcltkgrass/main/gui.tcl:
> 
> proc stop_monitors {} {
>     foreach monitor [search_xdrivers] {
>         exec d.mon start=$monitor >& /dev/null
>         exec d.mon stop=$monitor >& /dev/null
>         script_add "d.mon start=$monitor >& /dev/null" "cmd"
>         script_add "d.mon stop=$monitor >& /dev/null" "cmd"
>     }
> }
> 
> Since it's run without a controlling tty, and the monitor is already
> running when d.mon is asked to start it again, you get an error message
> in your mailbox from d.mon...
> 
> Anybody want to hit me with a clue stick as to why tcltkgrass would
> first try to start the monitor? only to kill it?

Eric,

just guessing:

In case you have running x3 only, the "for" loop would try to
close x0 (crash), x1 (crash), x2 (crash), x3 (o.k.) etc.
As d.mon -L is running now, we could use this to find the
running monitors. d.mon -L was failing with fifos (at least on Linux).

Markus

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'