From 83993240ac60bec52af829ba3dfdefc6930138e7 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 10 Nov 2000 16:32:09 +0000 Subject: [PATCH] Fix typos. --- doc/src/sgml/runtime.sgml | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 5391647586..eff4c1aa9a 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1217,12 +1217,12 @@ env PGOPTIONS='-c geqo=off' psql limits of the IPC resources then the postmaster will refuse to start up and should leave a marginally instructive error message about which problem was encountered and what needs to be done - about it. The relevant kernel parameters have a relatively - consistent nomenclature across systems; gives an overview. The methods to set them, however, vary; suggestions for some platforms are given - below. Be aware, however, that you will have to reboot your - machine at best, or possibly recompile the kernel, to change these + below. Be aware that you will have to reboot your + machine at least, possibly even recompile the kernel, to change these settings. @@ -1255,7 +1255,7 @@ env PGOPTIONS='-c geqo=off' psql SHMSEG Maximum number of shared memory segments per process - Must be at least 3, but the default is much higher. + must be at least 3, but the default is much higher @@ -1267,13 +1267,13 @@ env PGOPTIONS='-c geqo=off' psql SEMMNI Maximum number of semaphore identifiers (i.e., sets) - >= ceil(max_connections % 16) + >= ceil(max_connections / 16) SEMMNS Maximum number of semaphores system-wide - number of allowed connections, rounded up to multiple of 16 + max_connections rounded up to multiple of 16, + room for other applications @@ -1337,7 +1337,7 @@ env PGOPTIONS='-c geqo=off' psql The parameter SEMMNI determines the limit on the number of semaphore sets that can exist on the system at one time. Hence this parameter must be at least - ceil(max_connections % 16). Lowering the number of + ceil(max_connections / 16). Lowering the number of allowed connections is a temporary workaround for failures, which are usually confusingly worded No space left on device, from the function semget(). @@ -1351,7 +1351,7 @@ env PGOPTIONS='-c geqo=off' psql semaphores needs an entry. When a semaphore set is freed it is either added to an existing entry that is adjacent to the freed block or it is registered under a new map entry. If the map is - full, the freed semaphores gets lost (until reboot). Fragmentation + full, the freed semaphores get lost (until reboot). Fragmentation of the semaphore space could therefore over time lead to less available semaphores than there should be. @@ -1363,9 +1363,9 @@ env PGOPTIONS='-c geqo=off' psql - Various settings related to semaphore undo, such as - SEMMNU and SEMUME, are not of relevance - with Postgres. + Various other settings related to semaphore undo, such as + SEMMNU and SEMUME, are not of concern + for Postgres. @@ -1386,7 +1386,7 @@ env PGOPTIONS='-c geqo=off' psql /sys/sys/shm.h:69:#define SHMMAXPGS 1024 /* max hardware pages... */ - The default setting of 1024 is for a maximum of 4 MB of shared + The default setting of 1024 provides a maximum of 4 MB of shared memory. @@ -1457,7 +1457,7 @@ options "SEMMNU=120" to be enabled when the kernel is compiled. (They are by default.) The maximum size of shared memory is determined by the option SHMMAXPGS (in pages). The following - shows an example on how to set the various parameters: + shows an example of how to set the various parameters: options SYSVSHM options SHMMAXPGS=4096 -- 2.40.0