Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 3 May 2005 23:22:59 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: postgresql and sockets Message-ID: <20050503212259.GC31567@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050503091333 DOT GF25050 AT calimero DOT vinschen DOT de> <20050503131339 DOT GA27360 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On May 3 22:12, Krzysztof Duleba wrote: > Corinna Vinschen wrote: > > > I have the strange feeling that the file isn't recognized as socket > > anymore for some reason. When you called `cat /tmp/.s.PGSQL.5432', > > did you use Cygwin's cat? If the file would have been recognized as > > socket, you shouldn't have been able to read the content of the file. > > The correct result would have been: > > > > $ cat /tmp/.s.PGSQL.5432 > > cat: /tmp/.s.PGSQL.5432: No such device or address > > I used Cygwin's cat. The output above is what I get too when postgresql is > restarted. > > > So I'm wondering if something happened before the call to psql, so that > > the file has been... well, "downgraded" to a normal file instead of a > > socket file. Socket files have the system attribute set, for instance. > > If you remove this, the file is not recognized as socket file anymore. > > I sent another email that didn't make it to the list somehow. The point > was that the socket file breaks after some time (about 10 minutes) no > matter if it was used at all. So I might as well restart postgres, wait 10 > minutes, and it will be broken. > > In the meantime this line will appear in the postgresql's log: > > WARNING: dup(0) failed after 3195 successes: Bad file descriptor > > I'm not sure if it has anything to do. Hmm, there's no good reason for that, except if the number of open sockets or the number of sockets in the TIME_WAIT state is hitting a system limit. Normal dup2 on the socket works fine for me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/