appctl

Minor functionality enhancements were made in this release. It allows the use of pipes inside the ARGUMENTS parameter for a handler. This allows the piping of STDOUT through programs like 'sed' or to an external logging program.

The "statuscheck" action was introduced. This
action does the same as "status" or "pidlist" but
does not print anything on screen. Just the exit
value is set. The "pidlist" action now exits with
the same exit status as the "status" action. This
improves usability when used within an external
script or program. An extra linefeed at the end of
the output was removed.

This update adds some new features. It allows you to use pre-/post-start/stop/status scripts. Additionally, the function names for the "startup", "shutdown", and "status" shell function are now fully configurable. This update adds the ability to define a PIDFILE variable. If defined in a module environment file, it defines where the PID file is written or read from. This is useful if an application has a hard-coded PID path and cannot be reconfigured to use $PID_BASE/[module].pid.

This update addresses a bug where ctl showed a
handler that was not running when the PID of ctl
itself at execution time is a part of the handler
command line (handler name, path, or arguments).
For example, if the handler is called "handler5"
and the script got PID 5, then it was unable to
locate a running "handler5". Note that this
problem only occurs in pidless-mode. When PID
files are used (as per default) this problem will
not occur.

This update addresses a bug where ctl showed a non-running handler when the PID of ctl itself at execution time was a subset of the handler PID. For example, if the handler uses PID "4567" and ctl is executed on PID "456". This is very unlikely to happen, and only happens in PIDless mode where no PID files are used.