Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (64 - 66 of 431)

Ticket Resolution Summary Owner Reporter
#246 invalid IZ1611: Error with CVS bolzi
Description

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

        Issue #:      1611             Platform:     Other        Reporter: bolzi (bolzi)
       Component:     gridengine          OS:        Windows XP
     Subcomponent:    www              Version:      current         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    issues@gridengine
      QA Contact:     issues@gridengine
          URL:        http://gridengine.sunsource.net/servlets/BrowseList?list=users&by=thread&from=3389
       * Summary:     Error with CVS
   Status whiteboard:
      Attachments:

     Issue 1611 blocks:
   Votes for issue 1611:


   Opened: Mon May 9 11:35:00 -0700 2005 
------------------------


Hello,

i tried to download the current gridengine Version with WinCVS and TortoiseCVS.
Both programs return this error:

cvs [server aborted]: DomainFAQ.html,v is ambiguous; could mean domainFAQ.html,v
or DomainFAQ.html,v

because of this i can't download the complete source.
does anyone have an idea what is wrong or how the problem can be cleared?

Kind regards,

BoLzI

   ------- Additional comments from andreas Tue May 10 01:34:20 -0700 2005 -------
Changed subcomponent to 'www'.
See mail thread refered by issue URL for hints on a possible resolution.

   ------- Additional comments from crei Mon Nov 12 08:31:53 -0700 2007 -------
not my issue
#272 invalid IZ1789: Ambiguity in "Administering Policies" doc js631
Description

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

        Issue #:      1789             Platform:     All      Reporter: js631 (js631)
       Component:     gridengine          OS:        All
     Subcomponent:    doc              Version:      6.0u6       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     skonta
          URL:        http://gridengine.sunsource.net/servlets/ReadMsg?list=users&msgNo=12603
       * Summary:     Ambiguity in "Administering Policies" doc
   Status whiteboard:
      Attachments:

     Issue 1789 blocks:
   Votes for issue 1789:


   Opened: Mon Sep 12 08:32:00 -0700 2005 
------------------------


http://docs.sun.com/app/docs/doc/817-5677/6ml49n2bt?a=view#i999558

I just read through the "Sharing Functional Ticket Shares"
section.  In it it says:

  * Selecting the Share Functional Tickets check box means that
functional shares are replicated among jobs.

  * Clearing the Share Functional Tickets check box means that
functional shares are distributed among jobs.

Then in the following paragraph, it seems to contradict the above:

  "Jobs with many siblings that belong to the same category member
receive relatively small share portions if you select the Share
Functional Tickets check box. On the other hand, if you clear the
Share Functional Tickets check box, all sibling jobs receive the same
share amount as their category member."

Before I explain my confusion, the checkbox in the new qmon GUI is
labeled "Share Functional Shares".  Anyway, it would seem that "if you
clear the Share Functional Tickets check box, all sibling jobs receive
the same share amount as their category member" implies the first
bullet point, which requires the checkbox be selected.

   ------- Additional comments from surajp Thu Mar 5 05:15:31 -0700 2009 -------
Reassigning issue to Sandra...
#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.
Note: See TracQuery for help on using queries.