You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Suresh Subbiah (JIRA)" <ji...@apache.org> on 2015/10/08 07:16:27 UTC
[jira] [Assigned] (TRAFODION-1248) LP Bug: 1459474 - scanner
KernelPidMaxLimit check is off by one
[ https://issues.apache.org/jira/browse/TRAFODION-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Subbiah reassigned TRAFODION-1248:
-----------------------------------------
Assignee: Amanda Moran (was: Vladimir Berman)
> LP Bug: 1459474 - scanner KernelPidMaxLimit check is off by one
> ---------------------------------------------------------------
>
> Key: TRAFODION-1248
> URL: https://issues.apache.org/jira/browse/TRAFODION-1248
> Project: Apache Trafodion
> Issue Type: Bug
> Components: installer
> Reporter: Vladimir Berman
> Assignee: Amanda Moran
>
> The scanner KernelPidMaxLimit check is off by one:
> CHECK_CONFIG ::: KernelPidMaxLimit ::: Upper limit for kernel.pid_max setting ::: error ::: 65535 ::: int_ge :::
> /sbin/sysctl -n kernel.pid_max
> That is, the expected value should be 65536 rather than 65535.
> Explanation from Guy:
> Here's a description from http://unix.stackexchange.com/questions/124040/how-to-determine-the-max-user-process-value
> /proc/sys/kernel/pid_max (since Linux 2.5.34)
> This file specifies the value at which PIDs wrap around (i.e.,
> the value in this file is one greater than the maximum PID).
> The default value for this file, 32768, results in the same
> range of PIDs as on earlier kernels. On 32-bit platforms, 32768
> is the maximum value for pid_max. On 64-bit systems, pid_max
> can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately
> 4 million).
> The above is saying that this value specified the wrap around value. So a value of 32768 means that 32767 would be the max value.
> In our case, we want 65536 so that our max pid value is 65535.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)