You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/10/28 03:38:27 UTC

[jira] [Updated] (HTRACE-286) htraced: improvements to logging, daemon startup, and configuration

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

Colin Patrick McCabe updated HTRACE-286:
----------------------------------------
    Attachment: HTRACE-286.001.patch

> htraced: improvements to logging, daemon startup, and configuration
> -------------------------------------------------------------------
>
>                 Key: HTRACE-286
>                 URL: https://issues.apache.org/jira/browse/HTRACE-286
>             Project: HTrace
>          Issue Type: Improvement
>          Components: htraced
>    Affects Versions: 4.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HTRACE-286.001.patch
>
>
> htraced: improvements to logging, daemon startup, and configuration
> * htraced should log a startup message as the first thing it does, so that it can be obvious when a new htraced instance is starting.
> * Configuration keys that begin with {{htraced.}} should be honored only by htraced, not by the htrace tool or any other code.  This will allow us to configure the log file path separately for htraced versus the command-line tool.
> * htraced should attempt to open the configured HTTP port as the first thing it does.  This way, if there is another htraced instance running, we bail out early rather than potentially messing up the current running instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)