[ https://issues.apache.org/jira/browse/TS-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-563: ----------------------------- Fix Version/s: (was: 3.1.2) 3.2.0 > Incorrectly returned 0 status code from startup script even when TS fails to > start > ---------------------------------------------------------------------------------- > > Key: TS-563 > URL: https://issues.apache.org/jira/browse/TS-563 > Project: Traffic Server > Issue Type: Bug > Affects Versions: 2.1.5 > Environment: Linux > Reporter: Marcus Clyne > Priority: Trivial > Fix For: 3.2.0 > > > When using proxy.config.log2 values in records.config rather than the new > proxy.config.log values, TS fails to start (server/manager/cop), but a return > code of 0 is returned rather than 1 or something more meaningful. > I have also noticed instances when config errors have prevented server from > starting, even though manager and cop do. It would probably make sense to > have a non-zero error code for these two. > Perhaps it might be useful to have different return codes for whether > cop/manager/server start or not (e.g. 1=server not started, 2=manager not > started, 3=cop not started? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira