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

        Issue #:      97               Platform:     All           Reporter: chaubal (chaubal)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      current          CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     ferstl
          URL:
       * Summary:     exit code implications for various methods
   Status whiteboard:
      Attachments:

     Issue 97 blocks:
   Votes for issue 97:


   Opened: Wed Nov 21 13:49:00 -0700 2001 
------------------------


What happens when various methods exit with different error codes is not
documented in one place.

Script/method           exit code       consequence
=====================================================================
job script              0               success
                        99              requeue
                        rest            "success", exit code in accounting file

prolog/epilog           0               success
                        99              requeue
                        rest            queue error state, job requeued

parallel start          0               success
                        rest            queue set to error state, job requeued

parallel stop           0               success
                        rest            queue set to error state, job not

requeued

suspend                 0               success
                        rest            success, no special meaning

restart                 0               success
                        rest            success, no special meaning

terminate               0               success
                        rest            success, no special meaning

migrate                 0               success
                        rest            success, for kernel ckpt special meaning: ckpt was not
sucessfull, did not happen (but migration will happen by SGE)

checkpoint              0               success
                        rest            success, for kernel ckpt special meaning: ckpt was not
sucessfull, did not happen

clean                   0               success
                        rest            success, no special meaning

   ------- Additional comments from chaubal Thu Nov 29 16:53:12 -0700 2001 -------
duplicate of issue # 106

*** This issue has been marked as a duplicate of 106 ***

   ------- Additional comments from chaubal Thu Nov 29 16:54:09 -0700 2001 -------
wrong issue closed

   ------- Additional comments from andreas Thu Oct 21 07:15:10 -0700 2004 -------
That's a man page issue at first.

[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.

I just built 8.0.0a on a CentOS 5.6 x86_64 machine

While running the install scripts I ran into a repeatable issue. The install_execd script fails to start the sge_execd daemon - it complains about a missing "./active_jobs" folder inside the directory defined to be the exechost spool directory.

Steps to repeat:

1. Install qmaster normally, I used all the defaults except for choosing classic spooling and not installing the start-on-boot-scripts

2. Run ./install_execd and accept all the default suggestions for execd spoool location. This error will appear:

{{{Grid Engine execution daemon startup

Starting execution daemon. Please wait ...

Shutting down Grid Engine execution daemon

ls: /opt/sge/default/spool/dag/active_jobs: No such file or directory

Hit <RETURN> to continue >>

}}}

Not a fatal error as you can manually go into $CELL/common/ and manually run the sgeexecd start script and things will work fine.

However this may freak out new SGE users/installers