mirror of
https://github.com/postgres/postgres.git
synced 2025-05-05 09:19:17 +03:00
Doc: prefer sysctl to /proc/sys in docs and comments.
sysctl is more portable than Linux's /proc/sys file tree, and often easier to use too. That's why most of our docs refer to sysctl when talking about how to adjust kernel parameters. Bring the few stragglers into line. Discussion: https://postgr.es/m/361175.1661187463@sss.pgh.pa.us
This commit is contained in:
parent
6d05d575be
commit
eb0097c6f3
@ -1277,11 +1277,12 @@ default:\
|
|||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
On <productname>Linux</productname>
|
On <productname>Linux</productname> the kernel parameter
|
||||||
<filename>/proc/sys/fs/file-max</filename> determines the
|
<varname>fs.file-max</varname> determines the maximum number of open
|
||||||
maximum number of open files that the kernel will support. It can
|
files that the kernel will support. It can be changed with
|
||||||
be changed by writing a different number into the file or by
|
<literal>sysctl -w fs.file-max=<replaceable>N</replaceable></literal>.
|
||||||
adding an assignment in <filename>/etc/sysctl.conf</filename>.
|
To make the setting persist across reboots, add an assignment
|
||||||
|
in <filename>/etc/sysctl.conf</filename>.
|
||||||
The maximum limit of files per process is fixed at the time the
|
The maximum limit of files per process is fixed at the time the
|
||||||
kernel is compiled; see
|
kernel is compiled; see
|
||||||
<filename>/usr/src/linux/Documentation/proc.txt</filename> for
|
<filename>/usr/src/linux/Documentation/proc.txt</filename> for
|
||||||
|
@ -4944,7 +4944,7 @@ SubPostmasterMain(int argc, char *argv[])
|
|||||||
* If testing EXEC_BACKEND on Linux, you should run this as root before
|
* If testing EXEC_BACKEND on Linux, you should run this as root before
|
||||||
* starting the postmaster:
|
* starting the postmaster:
|
||||||
*
|
*
|
||||||
* echo 0 >/proc/sys/kernel/randomize_va_space
|
* sysctl -w kernel.randomize_va_space=0
|
||||||
*
|
*
|
||||||
* This prevents using randomized stack and code addresses that cause the
|
* This prevents using randomized stack and code addresses that cause the
|
||||||
* child process's memory map to be different from the parent's, making it
|
* child process's memory map to be different from the parent's, making it
|
||||||
|
Loading…
x
Reference in New Issue
Block a user