Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 14 Feb 2014 19:58:20 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12695268.1392406668218.45532.1392407900499@arcas>
In-Reply-To: <JIRA.12695268.1392406668218@arcas>
References: <JIRA.12695268.1392406668218@arcas>
Subject: [jira] [Commented] (ACCUMULO-2372) Use POSIX logger for STDERR and
 STDOUT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs commented on ACCUMULO-2372:
---------------------------------------------

That might be fair, but... /usr/bin/logger is POSIX. It's definitely there on Macs, and it's provided by the util-linux package on RPM-based systems.

This is the same package that provides 'su', 'mount', and 'login'. It's also the same package that provides 'kill', which we have no problem assuming exists.

So, if it's not there, I'd be *very* surprised as you'd probably be running some Linux-From-Scratch thing which is deliberately non-POSIX... and if that's the case, there's no telling how our scripts would behave on those systems... so, maybe it's not worth maintaining the ability to fall back to such fringe cases?

> 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)