You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2014/06/03 05:01:06 UTC

[jira] [Commented] (SENTRY-237) Support log4j configuration for Sentry service

    [ https://issues.apache.org/jira/browse/SENTRY-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016166#comment-14016166 ] 

Sravya Tirukkovalur commented on SENTRY-237:
--------------------------------------------

Looks like all the command line options which SentryMain does not recognize (the ones SentryService uses, for example) should follow the ones which it does because of stopAtNonOption=false.

So even this works: 
bin/sentry --command service --log4jConf /tmp/log4j.properties --conffile /tmp/sentry-site.xml

> Support log4j configuration for Sentry service
> ----------------------------------------------
>
>                 Key: SENTRY-237
>                 URL: https://issues.apache.org/jira/browse/SENTRY-237
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Prasad Mujumdar
>            Assignee: Arun Suresh
>         Attachments: SENTRY-237.1.patch
>
>
> The sentry service should support log4j configuration property file.



--
This message was sent by Atlassian JIRA
(v6.2#6252)