[
https://issues.apache.org/jira/browse/HAWQ-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230188#comment-15230188
]
ASF GitHub Bot commented on HAWQ-636:
-------------------------------------
GitHub user radarwave opened a pull request:
https://github.com/apache/incubator-hawq/pull/566
HAWQ-636. hawq check include /etc/security/limits.d
Tested config files in '/etc/security/limits.d', it works well with
different config file and different user if defined user domain.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/radarwave/incubator-hawq HAWQ-636
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/566.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #566
----
commit f8fe2cf88e0b529f2a48657e4c7c14b515580e7b
Author: rlei <r...@pivotal.io>
Date: 2016-04-07T10:16:42Z
HAWQ-636. hawq check include /etc/security/limits.d
----
> hawq check should read configurations in /etc/security/limits.d
> ---------------------------------------------------------------
>
> Key: HAWQ-636
> URL: https://issues.apache.org/jira/browse/HAWQ-636
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Command Line Tools
> Reporter: Radar Lei
> Assignee: Radar Lei
>
> Currently 'hawq check' only check configurations from
> /etc/security/limits.conf.
> We should also include the configuration files inside /etc/security/limits.d/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
