diff options
| -rw-r--r-- | doc/src/sgml/runtime.sgml | 11 | ||||
| -rw-r--r-- | src/backend/postmaster/postmaster.c | 2 |
2 files changed, 7 insertions, 6 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 5b2ab083b66..7fac9617ce7 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1355,11 +1355,12 @@ default:\ <itemizedlist> <listitem> <para> - On <productname>Linux</productname> - <filename>/proc/sys/fs/file-max</filename> determines the - maximum number of open files that the kernel will support. It can - be changed by writing a different number into the file or by - adding an assignment in <filename>/etc/sysctl.conf</filename>. + On <productname>Linux</productname> the kernel parameter + <varname>fs.file-max</varname> determines the maximum number of open + files that the kernel will support. It can be changed with + <literal>sysctl -w fs.file-max=<replaceable>N</replaceable></literal>. + 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 kernel is compiled; see <filename>/usr/src/linux/Documentation/proc.txt</filename> for diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index 4f153ae1c61..a8b3f5000c2 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -4908,7 +4908,7 @@ SubPostmasterMain(int argc, char *argv[]) * If testing EXEC_BACKEND on Linux, you should run this as root before * 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 * child process's memory map to be different from the parent's, making it |