Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (154 - 156 of 431)

Ticket Resolution Summary Owner Reporter
#546 fixed IZ2656: Fix to support JAVA_HOME discovery on alternatives-based systems paulmillar
Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2656]

        Issue #:      2656             Platform:     All       Reporter: paulmillar (paulmillar)
       Component:     gridengine          OS:        All
     Subcomponent:    build            Version:      current      CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    PATCH
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     Fix to support JAVA_HOME discovery on alternatives-based systems
   Status whiteboard:
      Attachments:
                      Date/filename:                                        Description:                                                                                      Submitted by:
                      Mon Jul 14 16:05:00 -0700 2008: fix-alternatives.diff Proposed patch to fix JAVA_HOME discovery on alternatives- (sym-link-) based systems (text/plain) paulmillar

     Issue 2656 blocks:
   Votes for issue 2656:


   Opened: Mon Jul 14 16:02:00 -0700 2008 
------------------------


Alternatives is a system that allows fine-grain control over which of different
(competing) applications to use for some particular activity.  This is achieved
by casting the command (typically /usr/bin/<cmd>) as a sym-link into a suitably
named file in /etc/alternatives/ directory, which is (itself) a sym-link to the
specific application; for example, /usr/bin/java is a sym-link to
/etc/alternatives/java, which might be a sym-link to
/usr/lib/jvm/java-6-sun/jre/bin/java.

When guessing a value for JAVA_HOME on alternatives-based systems, the current
aimk.site doesn't fare well.  It assumes a JAVA_HOME of /usr, which leads to
interesting build failures (as -I/usr/include/linux becomes appended to the
compilation flags).

The proposed patch fixes this by testing whether the java binary in the user's
path is a sym-link.  If so, following the sym-link to discover the actual
location of the JDK.

Cheers,

Paul.

Index: aimk.site
===================================================================
RCS file: /cvs/gridengine/source/aimk.site,v
retrieving revision 1.66
diff -u -r1.66 aimk.site
--- aimk.site   3 Jul 2008 15:14:14 -0000       1.66
+++ aimk.site   14 Jul 2008 23:01:49 -0000
@@ -157,6 +157,11 @@
 if ( ! $?JAVA_HOME ) then
    set JAVA_BIN = `which \java`

+   # Resolve any symbolic links to find true absolute path to the executable.
+   if ( -l "$JAVA_BIN" ) then
+       set JAVA_BIN = `readlink -f /usr/bin/java`
+   endif
+
    if ( -e "$JAVA_BIN" ) then
       set JAVAV = `$JAVA_BIN -version |& head -1`
       set JAVAV = `expr "$JAVAV" : 'java version "1\.\([0-9]\).*"'`

   ------- Additional comments from paulmillar Mon Jul 14 16:05:15 -0700 2008 -------
Created an attachment (id=179)
Proposed patch to fix JAVA_HOME discovery on alternatives- (sym-link-) based systems
#552 fixed IZ2668: Adding admin and submit hosts: seperated => separated Dave Love <d.love@…> templedf
Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2668]

        Issue #:      2668             Platform:     All      Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    install          Version:      6.2         CC:    None defined
        Status:       NEW              Priority:     P5
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    dom (dom)
      QA Contact:     dom
          URL:
       * Summary:     Adding admin and submit hosts: seperated => separated
   Status whiteboard:
      Attachments:

     Issue 2668 blocks:
   Votes for issue 2668:


   Opened: Mon Jul 21 15:28:00 -0700 2008 
------------------------


In the "Adding admin and submit hosts" section of the installation, "separated"
is misspelled as "seperated".
#556 fixed IZ2674: need a better way to control shadow daemon parameters templedf
Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2674]

        Issue #:      2674             Platform:     All           Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    qmaster          Version:      6.2              CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
          URL:
       * Summary:     need a better way to control shadow daemon parameters
   Status whiteboard:
      Attachments:

     Issue 2674 blocks:
   Votes for issue 2674:


   Opened: Wed Jul 23 04:45:00 -0700 2008 
------------------------


The shadow daemon behavior is controlled by a set of three environment
variables.  Because the shadow daemon is typically started by the
$SGE_ROOT/$SGE_CELL/common/sgemaster script during host initialization, there is
no way to set the variables before the script runs.  The current solution is to
edit the sgemaster file to set the variables before running the shadow daemon,
but that is a poor solution.

One solution would be to have a separate file in the common directory to set the
shadow daemon behavior.  Another solution would be to set the variables
explicitly at the top of the sgemaster script so that if one must edit the file,
it is obvious what to edit.

   ------- Additional comments from templedf Wed Jul 23 05:47:15 -0700 2008 -------
In the case of SMF, the above is the complete story.  Without SMF, it is
possible to also edit the RC script to add the environment variables.  The same
arguments apply, however.  In addition, both the SMF and non-SMF methods should
match, so I would discount editing the RC script as a real option.
Note: See TracQuery for help on using queries.