You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/05/17 19:35:16 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13660892#comment-13660892 ]
Leif Hedstrom commented on TS-1831:
-----------------------------------
Seeing that things works now, do we still need to fix this? Move it out to v3.5.0 for now?
> 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
>
> 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