Opened 17 years ago

Closed 8 years ago

#55 closed enhancement (invalid)

IZ304: sge_conf(5) binary_path not used for qrsh_starter

Reported by: andreas Owned by:
Priority: normal Milestone:
Component: sge Version: 5.3beta1
Severity: minor Keywords: qmaster
Cc:

Description

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

        Issue #:      304              Platform:     All           Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    qmaster          Version:      5.3beta1         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
          URL:
       * Summary:     sge_conf(5) binary_path not used for qrsh_starter
   Status whiteboard:
      Attachments:

     Issue 304 blocks:
   Votes for issue 304:


   Opened: Fri Jun 28 08:21:00 -0700 2002 
------------------------


DESCRIPTION:
The binary_path setting in local sge_conf(5) is
not considered when qrsh_starter
is started using rsh by qrsh. The man page says
binary_path is used in such a case.

sge_conf(5) binary_path is used for cluster tuning
purposes, as it can
be used to lower the load a NFS server is faced
with.

   ------- Additional comments from andreas Mon Jan 20 04:24:43 -0700 2003 -------
sge_conf(5) binary path does not apply to util bin binaries

   ------- Additional comments from andreas Fri Sep 10 02:28:08 -0700 2004 -------
WORKAROUND:
A symbolic link needs to be created to effectuate executable
pathes other than

    $SGE_ROOT/utilbin/<arch>/qrsh_starter

actually be used.


   ------- Additional comments from pollinger Fri Dec 9 08:32:28 -0700 2005 -------
Changed Subcomponent

Change History (1)

comment:1 Changed 8 years ago by dlove

  • Resolution set to invalid
  • Severity set to minor
  • Status changed from new to closed

binary_path isn't in current sge_conf

Note: See TracTickets for help on using tickets.