[
https://issues.apache.org/jira/browse/HBASE-12211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166235#comment-14166235
]
stack commented on HBASE-12211:
-------------------------------
Around here .out is ignored searched only if suspect out of memory or a
segfault or looking for JVM output.
.log has a bunch of other 'environment' stuff printed at startup like vitals on
the jvm, classpath, etc. Having all env stuff but the ulimit in .log would be
splitting where to look for info, don't you think?
> hbase-daemon.sh should direct the ulimit output to logout instead of loglog
> ---------------------------------------------------------------------------
>
> Key: HBASE-12211
> URL: https://issues.apache.org/jira/browse/HBASE-12211
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0
> Reporter: stanley shi
> Priority: Minor
>
> In the hbase-daemon.sh file line 199, it has the content:
> {quote}echo "`ulimit -a`" >> $loglog 2>&1{quote}
> The variable loglog is defined as:
> {quote}
> logout=$HBASE_LOG_DIR/$HBASE_LOG_PREFIX.out
> loggc=$HBASE_LOG_DIR/$HBASE_LOG_PREFIX.gc
> loglog="${HBASE_LOG_DIR}/${HBASE_LOGFILE}"
> {quote}
> For my understanding, this information should be printed to the "logout"
> variable; we should not mix this "ulimit" information with the actual log
> printed by hbase java program.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
