[GE issues] [Issue 2807] New - inadequate inst_qmaster/inst_execd diagnosis if binary and common packages are not in $SGE_ROOT

mpospisil michael.pospisil at sun.com
Fri Nov 21 15:13:17 GMT 2008


http://gridengine.sunsource.net/issues/show_bug.cgi?id=2807
                 Issue #|2807
                 Summary|inadequate inst_qmaster/inst_execd diagnosis if binary
                        | and common packages are not in $SGE_ROOT
               Component|gridengine
                 Version|6.0
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|install
             Assigned to|mpospisil
             Reported by|mpospisil






------- Additional comments from mpospisil at sunsource.net Fri Nov 21 07:13:17 -0800 2008 -------
The current SGE installation is designed to require SGE_ROOT pointing to the
root directory of the distribution and to be the parent directory of the <cell>
directory.

I suspect that the inadequate error checking was introduced with SGE 6.0! The
SGE 5.3 checked by default if this prerequsite is met.

The SGE 5.3 installation routine has a function which is called
"ProcessQsystRoot". In this shell function by default there is a checking if the
current working directory (the directory from which "inst_sge" is called)
matches the $SGE_ROOT directory.

In SGE 6.0/6.1 the shell function is in 

   util/install_modules/inst_common.sh:ProcessSGERoot()

The code where the check is done is protected by a if clause which only does
this check if the variable "strict" is set to true:

      # do not check for correct SGE_ROOT in case of -nostrict
      if [ "$strict" = true ]; then
      [...]

As the comment indicates a command line parameter "-nostrict" would overwrite
this behavior. However the SGE 6.0/6.1 installation routine does not anymore
support the parameter "-nostrict" nor there is any evidence in the entire
installation routine
that the variable "strict" is set at all.

This is the root cause in my opinion why this problem occurred.

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=36&dsMessageId=89378

To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list