[
https://issues.apache.org/jira/browse/HADOOP-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564972#comment-13564972
]
Arpit Gupta commented on HADOOP-9253:
-------------------------------------
bq. it's unclear why to write ulimit to $log at all
This is being added so we can debug issues related to limits being set for
user. Thus capturing in the log so the user can refer to them at a later time.
bq. 2. If writing ulimit to $log, why use head to truncate the output
{code}
head "$log"
{code}
Is something that existed before and hence i left it as is. I can certainly
change it to -20 but as you mention if there are errors in the nohup command it
will log to this file as well so changing it to printing 20 lines might not
help in that case.
> Capture ulimit info in the logs at service start time
> -----------------------------------------------------
>
> Key: HADOOP-9253
> URL: https://issues.apache.org/jira/browse/HADOOP-9253
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.1.1, 2.0.2-alpha
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-9253.branch-1.patch, HADOOP-9253.branch-1.patch,
> HADOOP-9253.patch
>
>
> output of ulimit -a is helpful while debugging issues on the system.
--
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
