[
https://issues.apache.org/jira/browse/TS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-972:
-----------------------------
Fix Version/s: (was: 3.1.1)
3.1.2
Moving these to 3.1.2 for now. please move back if they will be worked on asap
for 3.1.1.
> traffic_line should warn if a command didn't succeed
> ----------------------------------------------------
>
> Key: TS-972
> URL: https://issues.apache.org/jira/browse/TS-972
> Project: Traffic Server
> Issue Type: Improvement
> Components: Management API
> Affects Versions: 3.1.0, 3.0.1
> Reporter: Arno Toell
> Fix For: 3.1.2
>
>
> {{traffic_line}} is a handy tool to manage a traffic server instance. For
> example it is possible to retrieve and set configuration settings through
> command line like this:
> {code}
> root@wv-tmp2:/home/at# traffic_line -r proxy.config.http.server_port ; echo $?
> 81
> 0
> {code}
> However, some commans can be set, but aren't effective until the server is
> restarted, despite of ATS offering the _-x_ option to flush configuration and
> reread new settings:
> {code}
> root@wv-tmp2:/home/at# traffic_line -s proxy.config.http.server_port -v 80 ;
> echo $?
> 0
> root@wv-tmp2:/home/at# traffic_line -x ; echo $?
> 0
> {code}
> Trafficserver should possibly warn when setting such settings which aren't
> effective until the server is restarted and leave with a non-zero exit status
> for _-x_ in such cases.
> Moreover {{traffic_line}} does not work at all if the manager is not running:
> {code}
> # traffic_line -r proxy.config.http.server_port ; echo $?
> traffic_line: Variable Not Found
> 1
> {code}
> That's all right, but the error message shall be improved telling that. :)
--
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
