You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2013/05/17 19:41:16 UTC

[jira] [Updated] (TS-1831) traffic_logstats should not always require log dir access

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

James Peach updated TS-1831:
----------------------------

    Fix Version/s: 3.5.0

Yeh 3.5.0 is fine. I'm not getting to this any time soon.
                
> traffic_logstats should not always require log dir access
> ---------------------------------------------------------
>
>                 Key: TS-1831
>                 URL: https://issues.apache.org/jira/browse/TS-1831
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>            Reporter: James Peach
>             Fix For: 3.5.0
>
>
> When running "make check", the traffic_logstats test fails if the host system does not have a current Traffic Server installation:
> {code}
> FAIL: tests/test_logstats_json
> ==============================
> unable to change to log directory "/home/vagrant/build/proxy/var/log/trafficserver" [2 'No such file or directory']
>  please set correct path in env variable TS_ROOT
> {code}
> It's unreasonable for traffic_logstats to absolutely require the logdir to be present. We should investigate whether the chdir failure can be weakened to a warning instead of a hard error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira