[jira] [Reopened] (ACCUMULO-2372) Use POSIX logger for STDERR and STDOUT

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs reopened ACCUMULO-2372:
-----------------------------------------

Re-opening, because it might still be applicable to the separate accumulo service scripts that [~mikewalch] has been working on for 2.0 (ACCUMULO-4588).

Something like the following could work, if we wanted to separate the logs based on STDOUT and STDERR:

{code}
stdout_logcmd='logger -i -p user.info'
stderr_logcmd='logger -i -s -p user.err'
...
{ { $command | ${stdout_logcmd} ; } 2>&1 1>&3 | ${stderr_logcmd} ; } 3>&1;
{code}

Users could easily override the logger command with their own, if they wanted to do something differently.

> 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
>            Assignee: Christopher Tubbs
>              Labels: newbie
>             Fix For: 2.0.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.3.15#6346)