[GRASS5] Problem with sockets on Linux

Markus Neteler neteler at geog.uni-hannover.de
Mon Mar 12 11:55:15 EST 2001


On Mon, Mar 12, 2001 at 04:48:50PM +0100, Andrea Aime wrote:
> I've updated my files to last CVS, and now driver is working well.
> Thanks
> Andrea
Very good... 

> "Eric G. Miller" wrote:
> > 
> > On Fri, Mar 09, 2001 at 08:49:02AM +0100, Andrea Aime wrote:
> > 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,

are you planning to check in your new code for $HOME/.grass5/com/
? Then we could get rid of the "locks" directory. Or are there 
objections?

Regards

 Markus

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