commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DAEMON-175) Document procrun exit codes
Date Sat, 02 Oct 2010 10:28:32 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk updated DAEMON-175:
-------------------------------

    Priority: Minor  (was: Major)

The exit value for service applications has no real meaning except for the logging purposes.
There are currently different exit values, which purpose could be used for some textual description
but I don't consider that important.
What we should actually do is to get as much info from the system as possible when
the error occurs.
Exit values would have some sense eventually at install/configure time to allow third
part wrapper scrips to make some decision or error reporting on their own.


> Document procrun exit codes
> ---------------------------
>
>                 Key: DAEMON-175
>                 URL: https://issues.apache.org/jira/browse/DAEMON-175
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Procrun
>            Reporter: Sebb
>            Priority: Minor
>             Fix For: 1.0.3
>
>
> There does not seem to be any documentation of what the different procrun exit codes
mean.
> I think it would be useful to log a textual exit message as well as the numeric code,
for example:
> {code}
> if (someerror) {
>     rv = 123;
>     rm = "Someerror occurred";
> }
> ...
> if (rv)
>     apxLogWrite(APXLOG_MARK_ERROR "Commons Daemon procrun failed "
>                            "with exit value: %d - %s", rv, rm);
> The numeric exit codes should also be documented somewhere.
> ...
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message