[
https://issues.apache.org/jira/browse/ACCUMULO-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-2372.
-----------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.9.0)
In newer systems with systemd, this is a non-issue if the service is started
with a systemd unit. journald would log the console output in that case.
Ultimately, I think we should not do anything to capture these logs, and let
users decide how to capture STDOUT and STDERR when they launch Accumulo.
As such, I'll close this issue as "Won't Fix". I think using the POSIX logger
would be slightly better than what we have now, but not nearly as good as just
letting users decide what to do with this, and simplifying our scripts.
> 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
>
> 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.4#6332)
