You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "bwahn (JIRA)" <ji...@apache.org> on 2015/03/23 15:15:11 UTC
[jira] [Commented] (TS-1849) traffic_logstats does not accept
relative log file paths
[ https://issues.apache.org/jira/browse/TS-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375935#comment-14375935 ]
bwahn commented on TS-1849:
---------------------------
[~jpeach@apache.org], I tested like this :
squid.log located in "/opt/ats/var/log/trafficserver/". The path defined "CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver" as records.config.
{code}
/opt/ats/bin$ ./traffic_logstats squid.log
Traffic summary
Origin Server Hits Misses Errors
------------------------------------------------------------------------------
192.168.100.10 0 3 0
==============================================================================
...
...
{code}
I'm thinking traffic_logstats has already feature for supported relative path.
Could you explain more detail?
> traffic_logstats does not accept relative log file paths
> --------------------------------------------------------
>
> Key: TS-1849
> URL: https://issues.apache.org/jira/browse/TS-1849
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Reporter: James Peach
> Labels: newbie
> Fix For: 6.0.0
>
>
> From TS-1834, traffic_logstats pukes if you give it a relative path to a log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)