Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (46 - 48 of 431)

Ticket Resolution Summary Owner Reporter
#224 fixed IZ1443: code cleanup in builtin_starter.c:start_command() Dave Love <d.love@…> uddeborg
Description

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

        Issue #:      1443             Platform:     All     Reporter: uddeborg (uddeborg)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      6.0u3      CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    TASK
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     pollinger
          URL:
       * Summary:     code cleanup in builtin_starter.c:start_command()
   Status whiteboard:
      Attachments:
                      Date/filename:                     Description:                                                              Submitted by:
                      Fri Jan 28 07:36:00 -0700 2005: #  Patch to remove the pre_args_ptr completely. (text/plain)                 uddeborg
                      Fri Jan 28 07:38:00 -0700 2005: #2 Patch to use *pre_args_ptr++ as the technique to assign args (text/plain) uddeborg

     Issue 1443 blocks:
   Votes for issue 1443:


   Opened: Fri Jan 28 07:35:00 -0700 2005 
------------------------


While investigating a problem with submitting
commands (issue 1442) I was confused bu tye use of
a pointer pre_args_ptr in the function
start_command in
source/daemons/shepherd/builtin_starter.c.  It is
set to point to the first element of pre_args, but
is then used as an array.  This original array
pre_args could be used instead.  I get the
impression that somebody intended to assign
successive values with the "*ptr++" idiom, but
then changed his mind and used ordinary array
indexing instead, without removing the pointer
variable from the code.

It was a bit confusing when reading the code, so I
would suggest cleaning it up.  It could be changed
in one of two ways.  Either the pre_args_ptr could
be removed, and all indexing could be done from
the original array.  Or the *ptr++ technique could
be used.  I'll attach two possible patches, one
for each case.

   ------- Additional comments from uddeborg Fri Jan 28 07:36:44 -0700 2005 -------
Created an attachment (id=36)
Patch to remove the pre_args_ptr completely.

   ------- Additional comments from uddeborg Fri Jan 28 07:38:31 -0700 2005 -------
Created an attachment (id=37)
Patch to use *pre_args_ptr++ as the technique to assign args

   ------- Additional comments from uddeborg Fri Jan 28 07:40:33 -0700 2005 -------
Oh, please note that these patches also include the bug fix I suggest
in issue 1442.  Sorry for mixing the two things together.

   ------- Additional comments from sgrell Tue Dec 6 08:17:23 -0700 2005 -------
Changed the Subcomponent.

Stephan

   ------- Additional comments from pollinger Tue Mar 7 02:24:51 -0700 2006 -------
Changed "Issue type" to task
#230 fixed IZ1495: SGE daemons don't start at boot due to install problem on Java Desktop System dom
Description

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

        Issue #:      1495             Platform:     All      Reporter: dom (dom)
       Component:     gridengine          OS:        Linux
     Subcomponent:    install          Version:      5.3p5       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andy (andy)
      QA Contact:     dom
          URL:
       * Summary:     SGE daemons don't start at boot due to install problem on Java Desktop System
   Status whiteboard:
      Attachments:

     Issue 1495 blocks:
   Votes for issue 1495:


   Opened: Fri Mar 11 13:01:00 -0700 2005 
------------------------


I received an email from a user who tried to
install SGE 5.3p5 on JDS.
When installing SGE startup script, it states that
the following service is
required to install the startup script.



> We can install the startup script that
> Grid Engine is started at machine boot (y/n) [y] >>
>
> cp /home/sgeadmin/53p5/default/common/rcsge
/etc/init.d/rcsge
> /sbin/insserv /etc/init.d/rcsge
> insserv: Service afs has to be enabled for
service rcsge
> insserv: exiting now!
>


How can I add the aforementioned service (afs)?

BTW, the installation was completed successfully
and the SGE cluster is
functional. The only problem is that the startup
script didn't work at the reboot.

====

NOTE: it is filed OS version suse_linux_8.2
because there's no JDS entry in the OS version.

Suggested Fix:

hansup,

I already noticed that on a different machine with
a newer Suse
distribution.. It looks that the insserv binary
has changed. "afs" is
usually not available on systems and in the past
this caused no problems.

The "afs" requirement is already removed from the
6.0 startup scripts. It
can be safely deleted from the 5.3 start script
template
(util/startup_template) as well.

so the line

   # Required-Start: $network afs

can be changed to

   # Required-Start: $network
#240 fixed IZ1577: sge_conf man page error alan_carriou
Description

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

        Issue #:      1577             Platform:     All      Reporter: alan_carriou (alan_carriou)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      6.0u3       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     sge_conf man page error
   Status whiteboard:
      Attachments:

     Issue 1577 blocks:
   Votes for issue 1577:


   Opened: Wed Apr 20 02:57:00 -0700 2005 
------------------------


In the section "FORMAT" of the sge_conf man page, the "xterm" paragraph contains
the sentence "Each sge_execd(8) may use a private mail  agent." which looks like
a copy/paste from the "mailer" paragraph, and does not seem relevant in the
"xterm" paragraph.

   ------- Additional comments from pollinger Mon Mar 23 04:01:15 -0700 2009 -------
Changed Subcomponent to man
Note: See TracQuery for help on using queries.