[GRASS5] Volunteer wanted for CELL driver color problem

Markus Neteler neteler at geog.uni-hannover.de
Wed Apr 18 11:28:56 EDT 2001


On Wed, Apr 18, 2001 at 11:35:42AM -0300, Bob Covill wrote:
> Hi,
> 
> I just tried starting the CELL driver on my Linux machine and I still
> get the same error message ...
> 
> Usage:  CELL [-] "input_fifo output_fifo"
> No socket to connect to for monitor <CELL>.
> Problem selecting CELL. Will try once more
> No socket to connect to for monitor <CELL>.
Did you add the "sleep(1)" for testing purposes?
diff main.c main.c~
134d133
<           sleep(1);

 
> It sounds like you are experiencing a different problem than I am. Do
> you have a special monitorcap entry fort the CELL driver?  I think the
> key to the above error is on the fist line, which sounds like the CELL
> driver is being called incorrectly? 
Yes, it is called incorrectly. I had this once with XDRIVER, reason was
(if I recall correctly) that my "cvs up -dP" failed. You should check
this and look out for conflicts (and rerun the configure etc).

The monitorcap is unchanged for years and always working. This can't be
the reason (as the CELL driver sometimes works here).

I am still searching for a way to kill the busy socket. Otherwise I cannot
proceed with testing :-)

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