Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (85 - 87 of 431)

Ticket Resolution Summary Owner Reporter
#356 invalid IZ2049: qstat -F XML displays complexes inconsistently ovid
Description

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

        Issue #:      2049             Platform:     Sun      Reporter: ovid (ovid)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0u4       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     qstat -F XML displays complexes inconsistently
   Status whiteboard:
      Attachments:

     Issue 2049 blocks:
   Votes for issue 2049:


   Opened: Mon May 1 10:04:00 -0700 2006 
------------------------


qstat -F -XML displays complex attributes for different queues in different
orders.

The first queue has this order:


hl:arch hl:num_proc hl:mem_total hl:swap_total hl:virtual_total \
                     hl:load_avg hl:load_short hl:load_medium hl:load_long
hl:mem_free \
                     hl:swap_free hl:virtual_free hl:mem_used hl:swap_used
hl:virtual_used \
                     hl:cpu hl:np_load_avg hl:np_load_short hl:np_load_medium
hl:np_load_long \
                     qf:qname qf:hostname qc:slots qf:tmpdir qf:seq_no qf:rerun
qf:calendar \
                     qf:s_rt qf:h_rt qf:s_cpu qf:h_cpu qf:s_fsize qf:h_fsize
qf:s_data \
                     qf:h_data qf:s_stack qf:h_stack qf:s_core qf:h_core qf:s_rss \
                     qf:h_rss qf:s_vmem qf:h_vmem qf:min_cpu_interval"

but the other queues have this order:


 hl:load_avg hl:load_short hl:load_medium hl:load_long \
                     hl:arch hl:num_proc hl:mem_free hl:swap_free hl:virtual_free \
                     hl:mem_total hl:swap_total hl:virtual_total hl:mem_used \
                     hl:swap_used hl:virtual_used hl:cpu hl:np_load_avg \
                     hl:np_load_short hl:np_load_medium hl:np_load_long \
                     qf:qname qf:hostname qc:slots qf:tmpdir qf:seq_no qf:rerun \
                     qf:calendar qf:s_rt qf:h_rt qf:s_cpu qf:h_cpu qf:s_fsize \
                     qf:h_fsize qf:s_data qf:h_data qf:s_stack qf:h_stack \
                     qf:s_core qf:h_core qf:s_rss qf:h_rss qf:s_vmem \
                     qf:h_vmem qf:min_cpu_interval"

This inconsistency makes it hard to program the XML parser for qstat -F -xml.
#357 fixed IZ2058: shell_start_mode should be documentated to be only used for batch jobs roland
Description

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

        Issue #:      2058             Platform:     Sun      Reporter: roland (roland)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      6.0         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     shell_start_mode should be documentated to be only used for batch jobs
   Status whiteboard:
      Attachments:

     Issue 2058 blocks:
   Votes for issue 2058:


   Opened: Mon May 22 01:24:00 -0700 2006 
------------------------


The shell_start_mode in described queue_conf(5) but the man page. From the man
page a user could think the option affects all jobs but that's not true. The
shell_start_mode is only used for batch jobs submitted by qsub and is not used
for interactive jobs submitted by qrsh/qsh/qlogin.
#358 fixed IZ2059: shared library name DT_SONAME not set with libdrmaa.so andreas
Description

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

        Issue #:      2059             Platform:     All      Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    drmaa            Version:      6.0         CC:    None defined
        Status:       STARTED          Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    templedf (templedf)
      QA Contact:     templedf
          URL:        http://gridengine.sunsource.net/servlets/BrowseList?list=dev&by=thread&from=12304
       * Summary:     shared library name DT_SONAME not set with libdrmaa.so
   Status whiteboard:
      Attachments:

     Issue 2059 blocks:
   Votes for issue 2059:


   Opened: Tue May 23 07:57:00 -0700 2006 
------------------------


DESCRIPTION:
Under Linux there is a ld(1) option

-soname=name
  When creating an ELF shared  object,  set  the  internal
  DT_SONAME field  to  the specified name.  When an executable is linked
  with a shared object which has a DT_SONAME field, then when the
  executable is  run  the  dynamic linker will attempt to load the shared
  object specified by the DT_SONAME field rather than  the  using  the
  file name given to the linker.

for setting a shared libraries DT_SONAME.

An application linked with a shared library with DT_SONAME
can detect at deployment time, if the library in LD_LIBRARY_PATH
has the right version. Without DT_SONAME being set it can occur
the application starts though, but shows strange error behaviour
during run-time.

COMMENTS:
Until now (6.0u8) libdrmaa.so delivered with N1GE is of version 0.95.
It is planned though to deliver in future releases a DRMAA 1.0 library
*plus* the old 0.95 compliant one.

WORKAROUND:
As workaround the application shall use drmaa_version() to ensure
LD_LIBRARY_PATH libdrmaa.so has the correct version.

   ------- Additional comments from andreas Tue May 23 08:20:43 -0700 2006 -------
There is a related problem with libdrmaa.so 0.95/1.0:

I just encountered libdrmaa.0.95.so (maintrunk) even had linking
symbols

   int drmaa_get_num_attr_names(drmaa_attr_names_t* values, int *size);
   int drmaa_get_num_attr_values(drmaa_attr_values_t* values, int *size);
   int drmaa_get_num_job_ids(drmaa_job_ids_t* values, int *size);

even though these functions actually are DRMAA 1.0 specific. I fixed
it (maintrunk). Now at least DRMAA 1.0 applications will fail with a
more reasonable error message, in case LD_LIBRARY_PATH libdrmaa is 0.95.


   ------- Additional comments from andreas Tue May 23 09:03:20 -0700 2006 -------
Added URL to thread with details on how to solve the -soname issue.

   ------- Additional comments from andreas Mon May 29 00:28:05 -0700 2006 -------
Fixed for in Maintrunk and S2-branch for Solaris and Linux
Note: See TracQuery for help on using queries.