You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2014/02/14 20:42:35 UTC
[jira] [Commented] (ACCUMULO-2372) Use POSIX logger for STDERR and
STDOUT
[ https://issues.apache.org/jira/browse/ACCUMULO-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901846#comment-13901846 ]
Mike Drob commented on ACCUMULO-2372:
-------------------------------------
We should also have a fall back option of using .out and .err files if {{/usr/bin/logger}} does not exist.
> Use POSIX logger for STDERR and STDOUT
> --------------------------------------
>
> Key: ACCUMULO-2372
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2372
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Christopher Tubbs
> Fix For: 1.7.0
>
>
> Instead of piping STDOUT and STDERR to *.out and *.err files in our launch scripts, we should pipe to the POSIX cli logger (/usr/bin/logger) to log to the system logging facility at the desired log level.
> Incorporating the system logging facilities is useful for system administrators for troubleshooting and/or auditing. More integration with external logging facilities also means that we reduce our responsibility to maintain/manage the resulting logs to avoid problems (like filling up the local file system with logs), deferring that to utilities dedicated to that responsibility.
> The command-line options used for /usr/bin/logger should be enough to associate the logs with the particular process.
> (NOTE: Log4j can also be configured to use the system log facility, but that should be done through log4j configuration, with the appropriate log appender.)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)