Update spoofing /tmp symlink instructions to be more specific about the

name of the needed symlink file.

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index d487758020308fe77efc9513a8f9f2fdd3a1ca0e..ab688099c3fd2c46c2b7f9de7035d68eda0b9a9d 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Operating System Environment
@@ -1398,10 +1398,10 @@ $ kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`
    linkend="guc-unix-socket-directory">) that has write permission only
    for a trusted local user.  This prevents a malicious user from creating
    their own socket file in that directory.  If you are concerned that
-   some applications might still look in /tmp for the
-   socket file and hence be vulnerable to spoofing, create a symbolic link
-   during operating system startup in /tmp that points to
-   the relocated socket file.  You also might need to modify your
+   some applications might still reference /tmp for the
+   socket file and hence be vulnerable to spoofing, during operating system
+   startup create symbolic link /tmp/.s.PGSQL.5432 that points
+   to the relocated socket file.  You also might need to modify your
    /tmp cleanup script to preserve the symbolic link.