From: | Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com> |
---|---|
To: | Steve Wolfe <steve(at)iboats(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Ah, yet another cause for not binding the right port.... |
Date: | 2000-06-10 14:04:13 |
Message-ID: | 39424ADD.1B95C4E3@cupid.suninternet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Wolfe wrote:
> When postgres binds to any port, it likes to write a file in /tmp, along
> the lines of ".s.PGSQL.5432". If /tmp is not writeable by the postgres
Just in case you missed it, that file in /tmp is not a real file, but
a "socket" (Unix domain).
> process, it will not be able to bind to any port. However, it doesn't give
> you an intelligent error message like "Can't create file", it simply says
> that it can't bind the port, and of course, asks if another postgres
> process is already running.
If the node is there, it can't "bind" to the "port". Ofcourse, you
just delete it to mix it :)
--
Martijn van Oosterhout <kleptog(at)cupid(dot)suninternet(dot)com>
http://cupid.suninternet.com/~kleptog/
From | Date | Subject | |
---|---|---|---|
Next Message | lampe | 2000-06-10 15:58:17 | libpgtcl.so? Called by pgaccess. |
Previous Message | lampe | 2000-06-10 01:49:33 | RE: FIXED: Cannot INDEX an Access97 ODBC export? |