[
https://issues.apache.org/jira/browse/YETUS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236010#comment-16236010
]
Sean Busbey commented on YETUS-570:
-----------------------------------
{code}
175 NOTE: The actual implementation of this feature is dependent upon the
version of Bash. For bash v4 and higher (most operating systems), the fork
bomb protection is generally only used for the build and QA tools. This means
Apache Yetus should itself will continue to function. For earlier versions of
bash (e.g., OS X), the limit is applied to all of test-patch. If the limit is
hit, Apache Yetus will itself likely crash.
176
{code}
This means Apache Yetus should -itself will- continue to function
> Report and optionally kill stale JVMs between unit test modules
> ---------------------------------------------------------------
>
> Key: YETUS-570
> URL: https://issues.apache.org/jira/browse/YETUS-570
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Affects Versions: 0.6.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Attachments: YETUS-570.03.patch, YETUS-570.wip.00.patch,
> YETUS-570.wip.01.patch, YETUS-570.wip.02.patch
>
>
> YETUS-561 does a great job of preventing fork bombs and stale processes from
> destroying machines. However, Yetus should do a better job of:
> a) Reporting when that happens
> b) Preventing that from happening
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
