|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.393 2007/12/22 05:13:03 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.394 2007/12/23 03:10:04 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter Id="runtime"> |
4 | 4 | <title>Operating System Environment</title> |
@@ -1359,18 +1359,18 @@ $ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput |
1359 | 1359 | </screen> |
1360 | 1360 | </para> |
1361 | 1361 |
|
1362 | | -<important> |
1363 | | - |
1364 | | -It is best not to use <systemitem>SIGKILL</systemitem> to shut down |
1365 | | -the server. Doing so will prevent the server from releasing |
1366 | | -shared memory and semaphores, which might then have to be done |
1367 | | -manually before a new server can be started. Furthermore, |
1368 | | -<systemitem>SIGKILL</systemitem> kills the <command>postgres</command> |
1369 | | -process without letting it relay the signal to its subprocesses, |
1370 | | -so it will be necessary to kill the individual subprocesses by hand as |
1371 | | -well. |
1372 | | -</para> |
1373 | | -</important> |
| 1362 | + <important> |
| 1363 | + <para> |
| 1364 | + It is best not to use <systemitem>SIGKILL</systemitem> to shut down |
| 1365 | + the server. Doing so will prevent the server from releasing |
| 1366 | + shared memory and semaphores, which might then have to be done |
| 1367 | + manually before a new server can be started. Furthermore, |
| 1368 | + <systemitem>SIGKILL</systemitem> kills the <command>postgres</command> |
| 1369 | + process without letting it relay the signal to its subprocesses, |
| 1370 | + so it will be necessary to kill the individual subprocesses by hand as |
| 1371 | + well. |
| 1372 | + </para> |
| 1373 | + </important> |
1374 | 1374 | </sect1> |
1375 | 1375 |
|
1376 | 1376 | <sect1 id="encryption-options"> |
|