Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 431)

Ticket Resolution Summary Owner Reporter
#154 fixed IZ924: include example of host_aliases in .../common Dave Love <d.love@…> chaubal
Description

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

        Issue #:      924              Platform:     All       Reporter: chaubal (chaubal)
       Component:     gridengine          OS:        All
     Subcomponent:    install          Version:      6.0beta      CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    TASK
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     dom
          URL:
       * Summary:     include example of host_aliases in .../common
   Status whiteboard:
      Attachments:

     Issue 924 blocks:
   Votes for issue 924:


   Opened: Thu Mar 25 09:20:00 -0700 2004 
------------------------


The common directory contains samples of all the
various configuration files which can be
optionally used: sge_request, qtask, sge_aliases.
 However, it contains no sample for host_aliases.

It makes sense to provide a sample host_aliases
file, for the sake of completeness.

   ------- Additional comments from andreas Tue Mar 29 08:49:33 -0700 2005 -------
Changed to install.
#155 fixed IZ933: not allowed -masterq switch for serial jobs accepted Dave Love <d.love@…> andy
Description

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

        Issue #:      933              Platform:     All       Reporter: andy (andy)
       Component:     gridengine          OS:        All
     Subcomponent:    qmaster          Version:      6.0beta      CC:    None defined
        Status:       NEW              Priority:     P5
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     ernst
          URL:
       * Summary:     not allowed -masterq switch for serial jobs accepted
   Status whiteboard:
      Attachments:

     Issue 933 blocks:
   Votes for issue 933:


   Opened: Tue Mar 30 07:37:00 -0700 2004 
------------------------


The -masterq switch is only supported for parallel
jobs. For non parallel jobs the switch may not be
accepted.

The current behavipr is to accept the switch but
not to adhere to the given -masterq.

Workaround: Do not use the -mqasterq switch for
non parallel jobs.

   ------- Additional comments from andreas Tue Mar 30 10:04:40 -0700 2004 -------
Current behaviour is well documented in qsub(1)

     -masterq queue,...
          Available for qsub, qrsh, qsh, qlogin and qalter.  Only
          meaningful  for  parallel  jobs, i.e. together with the
          -pe option.

thus lowering priority to P4.

   ------- Additional comments from andreas Mon Apr 5 10:14:02 -0700 2004 -------
lowering prio

   ------- Additional comments from roland Mon Dec 5 09:51:32 -0700 2005 -------
The verification should be done on qmaster site and not on client site.

The parsing on client site is done in alphabetical order. On parsing the
-masterq switch the rejection can't be done because the -pe can follow and on
the -pe parsing the rejection can't be done because -masterq is not necessary.

   ------- Additional comments from ernst Tue Dec 13 02:41:55 -0700 2005 -------
Changed Priority
#158 fixed IZ949: When qconf fails during installation, the diagnostic is incorrect uddeborg
Description

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

        Issue #:      949              Platform:     All       Reporter: uddeborg (uddeborg)
       Component:     gridengine          OS:        All
     Subcomponent:    install          Version:      6.0beta      CC:    None defined
        Status:       VERIFIED         Priority:     P3
      Resolution:     FIXED           Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andy (andy)
      QA Contact:     dom
          URL:
       * Summary:     When qconf fails during installation, the diagnostic is incorrect
   Status whiteboard:
      Attachments:

     Issue 949 blocks:
   Votes for issue 949:


   Opened: Fri Apr 2 07:27:00 -0700 2004 
------------------------


When I tried to install the beta on a host, the
procedure failed during the "Checking hostname
resolving" phase.  After failing, it prints "The
error message was:" and then the usage message
from qconf.

Trying to trace this a little, I came across this
code in CheckHostNameResolving() in inst_execd.sh

      $SGE_BIN/qconf -sh > /dev/null 2>&1
      if [ $? = 1 ]; then
         errmsg=`$SGE_BIN/qconf 2>&1`
      else
         errmsg=`$SGE_BIN/qconf -sh 2>&1 |  grep
denied:`
      fi

Here first qconf is run with the "-sh" flag.  Then
 when it fails, it is run again, in order to
capture the error message.  But if the exit code
was 1, it is run without the -sh flag, which seems
like the bug.  Ran in this way it does give the
usage message, but it is not the error message it
got (and discarded) in the first attempt.

   ------- Additional comments from andy Tue Apr 6 00:58:46 -0700 2004 -------
Fixed.

Call "qconf -sh" in case of error.

   ------- Additional comments from uddeborg Wed Apr 28 04:27:21 -0700 2004 -------
I've now verified the fix in beta 2.  (Am I, as a reporter, supposed
to do this step?  Should I be the one closing too/instead?)
Note: See TracQuery for help on using queries.