[GRASS5] GRASS Monitor

Malcolm Blue mblue at nb.sympatico.ca
Tue Apr 17 23:46:13 EDT 2001


Hi,

The best place to look to get started is:

http://www.geog.uni-hannover.de/grass/firsttime.html

This has links to sample data, tutorials and other useful information, plus has
some basic information to get you started.

Enjoy,

Malcolm


ja id wrote:

> hello ,
> i had been download grass5 in linux platform but it can't running completely
> .it wanna location,mapset and database...what would i do..and how i'm going
> to do...
>
> >From: "Eric G. Miller" <egm2 at jps.net>
> >Reply-To: grass5 at geog.uni-hannover.de
> >To: grass5 at geog.uni-hannover.de
> >Subject: Re: [GRASS5] GRASS Monitor
> >Date: Tue, 17 Apr 2001 18:27:53 -0700
> >
> >On Tue, Apr 17, 2001 at 02:43:22PM -0300, Bob Covill wrote:
> > > Hello,
> > >
> > > This is probably a question for Eric.
> > >
> > > I have a recent version of GRASS on Linux (RedHat 6.1). The system is
> > > 300 MHz with 200 MB RAM. Everything works fine on this system.
> > >
> > > I then moved the GRASS build to a faster machine (PIII with 500 MB RAM)
> > > also running RedHat Linux. Again, everything worked fine with the
> > > exception of the monitor. The monitor (sockets) would start but complain
> > > that the socket was unavailable or in use by another program.
> > >
> > > I discovered the source of the problem was that d.mon was trying to
> > > select the monitor before it had completely started. I was able to work
> > > around the problem by executing "d.mon -s start=x0" followed by "d.mon
> > > select=x0".
> > >
> > > Any thoughts on why this might be happening?
> >
> >Nail on head.  Faster machine, executes more code during time slice,
> >oops socket or server is not ready to accept connections.  Anyway, 'bout
> >the only thing I can think of is to have d.mon sleep() for a little
> >while before trying to connect or after the first attempt failing.  It
> >may be a little trial an error to decide how many seconds and/or if the
> >iterations of "try" should be increased.  One second after first failure
> >might be sufficient.  I only know that the CELL/PNG drivers are much
> >slower to start up than the X driver.
> >
> >If I wanted to get tricky, I would try to find out if the monitor is
> >running from the process list and try harder to connect if it is, or
> >just quit right away if it isn't.  But I think the sleep() hack should
> >be sufficient.
> >
> >grass/src/display/d.mon/cmd/main.c
> >
> >..
> >128     if (select->answer)
> >129     {
> >130         oops = run("select", select->answer); /* couldn't select */
> >131         if (oops && start->answer && strcmp (start->answer,
> >               select->answer) == 0) /* try once more */
> >132         {
> >133             fprintf (stderr, "Problem selecting %s. Will try
> >                       once more\n", select->answer);
> >+++             sleep(1);
> >134             oops = run("select", select->answer); /* couldn't
> >                         select */
> >135         }
> >..
> >
> >P.S. Sorry, been a bit distracted from GRASS lately...
> >
> >--
> >Eric G. Miller <egm2 at jps.net>
> >
> >----------------------------------------
> >If you want to unsubscribe from GRASS Development Team mailing list write
> >to:
> >minordomo at geog.uni-hannover.de with
> >subject 'unsubscribe grass5'
> >
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> ----------------------------------------
> If you want to unsubscribe from GRASS Development Team mailing list write to:
> minordomo at geog.uni-hannover.de with
> subject 'unsubscribe grass5'


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



More information about the grass-dev mailing list