[logback-dev] [JIRA] Resolved: (LBCORE-31) "Watching" the config file

Ceki Gulcu (JIRA) noreply-jira at qos.ch
Mon Oct 27 12:29:21 CET 2008

     [ http://jira.qos.ch/browse/LBCORE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCORE-31.

    Resolution: Duplicate

> "Watching" the config file
> --------------------------
>                 Key: LBCORE-31
>                 URL: http://jira.qos.ch/browse/LBCORE-31
>             Project: logback-core
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: unspecified
>         Environment: Operating System: Windows
> Platform: PC
>            Reporter: Ted Graham
>            Assignee: Logback dev list
> I build server applications and when something goes wrong, I need to be able to enable logging and have the application notice the change without a restart.  My application have no gui, so manually "poking" the application is awkward and ugly.  
> Note that I disagree with the suggestion to check if the file has changed on each log statement.  My application's performance goals are measured in microseconds (time to respond to a message by sending another message), any additional latency is a big problem for me.  I'd like to be able to configure the frequency of checking the file, but it isn't super important.  
> Ideally, I'd like to be able to specify that the config file should be watched IN the config file, rather than programatically.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list