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/12/10 20:30:09 UTC
[jira] [Resolved] (TS-2424) fix broken manager diagnostics
[ https://issues.apache.org/jira/browse/TS-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach resolved TS-2424.
-----------------------------
Resolution: Fixed
> fix broken manager diagnostics
> ------------------------------
>
> Key: TS-2424
> URL: https://issues.apache.org/jira/browse/TS-2424
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, Logging, Quality
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 4.2.0
>
>
> The diagnostic logging was broken by a build change made by {{efe90f3fecb10605f35bbfe557f19534b9e6fce7}}. In the original build, the digs subsystem was built multiple times for {{traffic_server}} and {{traffic_server}} with different preprocessor flags. Now that {{DiagsConfig.cc}} is built into a convenience library, this does not happen, and {{manager.log}} is no longer created.
> The commit that broke this actually moved the build in the right direction, so I'm just going to finish that off. We can make a new library, {{libdiags.a}} that depends on both {{lib's.a}} and {{librecords.a}}. {{traffic_server}} and {{traffic_manager}} can both link against this and make the configuration change at runtime.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)