[
https://issues.apache.org/jira/browse/HADOOP-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601075#comment-13601075
]
Hudson commented on HADOOP-9379:
--------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #552 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/552/])
HADOOP-9379. capture the ulimit info after printing the log to the console.
(Arpit Gupta via suresh) (Revision 1455519)
Result = UNSTABLE
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1455519
Files :
*
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/bin/hadoop-daemon.sh
*
/hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/bin/yarn-daemon.sh
> 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
