[GRASS5] Problem with sockets on Linux

[Eric G. Miller]

On Fri, Mar 09, 2001 at 08:49:02AM +0100, Andrea Aime wrote:
> No, the server is not running, I can't find any new process (I don't
> know the driver name (is it simply "xo"?), but if you sort processes 
> by PID you see if something has been created after grass start). 
> The following "d.mon select=x0" of course does not work and returns
> the same error.
> Hope this helps
> Andrea

I think the problem is d.mon isn't getting built properly for some
reason.  I change the arguments for "start" if the USE_G_SOCKS symbol
is defined.  I think the drivers are being called with all the fifo
args, so they are exiting (do you get a "Usage" message?).

> PS: which server ports are used by the X driver? Maybe it finds them
> occupied by another application (I use 4444/6001/7001 for an in-house 
> application...). Anyway, I think that server ports numbers should be
> configurable...

No ports are used.  Just local UNIX socket files.  I figured UNIX
sockets are simpler and there'd be no reason another user should ever
"connect" to a display driver started by someone else.  Also, UNIX
sockets should be faster since the kernel has to do less work (mearly
queues up data in a buffer from write() and pops the data to the
application on read()).  Socket files currently live in
<mapset>/.tmp/<host>/<driver_name>

-- 
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'