[Spread-users] Increasing MAX_GROUP_NAME causes problems, defined twice... and different

Jacob Green jgreen at spreadconcepts.com
Fri Jul 20 11:27:45 EDT 2007

You can change MAX_GROUP_NAME to be 64 if you want.  Just make sure you
update it in both places and that they match.  If they don't match, then yes
it will break stuff.


-----Original Message-----
From: spread-users-bounces at lists.spread.org
[mailto:spread-users-bounces at lists.spread.org] On Behalf Of Brad Larson
Sent: Friday, July 20, 2007 8:38 AM
To: spread-users at lists.spread.org
Subject: [Spread-users] Increasing MAX_GROUP_NAME causes problems,defined
twice... and different

Compiled from  spread-src-3.17.4  (I'm not using 4.x because I'm also 
using the SpreadModule with python on linux and windows)

I would like to increase MAX_GROUP_NAME from 32 to 64. In searching the 
archives I have found the following question on (that was never answered).

       Fri Feb 3 12:24:36 EST 2006
       [Spread-users] Increasing the MAX_GROUP_NAME and/or the   

Looking at the code it appears that MAX_GROUP_NAME is defined twice!

In sp.h
    #define         MAX_GROUP_NAME          64   /* was 32 */

in spread_params.h

    #define         MAX_PRIVATE_NAME        10 /* largest possible size 
of private_name field of SP_connect() */
    #define         MAX_PROC_NAME           20   /* largest possible 
size of process name of daemon */
    #define         MAX_GROUP_NAME           
                                   /* #private_name#proc_name  including 
the null */

With MAX_PRIVATE_NAME and MAX_PROC_NAME defined as listed they happen to 
match the original MAX_GROUP_NAME at 32.
Ensuring that both definitions match the largest of the two definitions 
appears be the best course.  Will this break anything else I'm not 

Spread-users mailing list
Spread-users at lists.spread.org

More information about the Spread-users mailing list