GRASS4.1/Solaris2.2 performance

[Olga Waupotitsch]

In info.grass.user you write:

>Jean Boiven,

>Now that you have got GRASS4.1 running on Solaris 2.2, I would appreciate 
>an appraisal of how it performs, compared to your previous version of GRASS
>on another OS.

>For those of you deciding whether to go with Solaris 2.2 in the near
>future, here's news of another dud in the GRASS4.1/Solaris 2.2 story:

>r.poly does not work, it bombs out with a "BUS error" message.

>It is NOT a memory problem, it doesn't work on any size raster image.

>As I have yet to run any software on the SPARClassic designed specifically
>for Solaris 2.2, it would be premature to announce the machine and the
>operating system failures, but GRASS4.1 is a pig on Solaris 2.2.

>Let's see: mapgen4---- NO
>	   v.digit---- NO
>	   v.digit2--- almost useless
>	   r.poly ---- NO
>	   r.watershed -- NO
>	   XDRIVER -- compiles incorrectly 
>	   built-in database capabilities -- none
>Relative speed compared to GRASS4.0 on an 386i with SunOS 4.0.2:
>				--same or slower
>Relative speed compared to GRASS4.x on an IPX with Solaris 1.x:
>				--MUCH slower
>Oh well, it's free!

>^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
>   Ronald Thomas                         ^  ront at meeker.cfnr.colostate.edu
>    Natural Resources Spec. (GIS)        ^  
>     Resources Management Division       ^   Phone: 303-586-3565  x285
>      Rocky Mountain National Park       ^          700-323-7285  (FTS)
>       Estes Park, CO  80517             ^   FAX:   303-586-4702
>^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
We are working on GRASS4.1 for Solaris

One thing I can tell you right now is that
to compile XDRIVER substitute 
   setpgrp(0, getpid());
by
   setsid()
Please tell me if it worked.
what about v.digit, r.poly and r.watershed?
do they compile and run incorrectly?
Olga