You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2013/04/07 00:41:16 UTC
[jira] [Commented] (HADOOP-9379) capture the ulimit info after
printing the log to the console
[ https://issues.apache.org/jira/browse/HADOOP-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624524#comment-13624524 ]
Konstantin Boudnik commented on HADOOP-9379:
--------------------------------------------
It is marked for 2.0.4-alpha, but never made it in. Committing.
> capture the ulimit info after printing the log to the console
> -------------------------------------------------------------
>
> Key: HADOOP-9379
> URL: https://issues.apache.org/jira/browse/HADOOP-9379
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.2.0, 2.0.4-alpha
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Priority: Trivial
> Fix For: 1.2.0, 0.23.7, 2.0.5-beta
>
> Attachments: HADOOP-9379.branch-1.patch, HADOOP-9379.patch
>
>
> Based on the discussions in HADOOP-9253 people prefer if we dont print the ulimit info to the console but still have it in the logs.
> Just need to move the head statement to before the capture of ulimit code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira