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 To: cygwin AT cygwin DOT com From: "Krzysztof Duleba" Subject: Re: postgresql and sockets Date: Mon, 9 May 2005 20:45:46 +0200 Lines: 37 Message-ID: References: <20050503091333 DOT GF25050 AT calimero DOT vinschen DOT de> <20050503131339 DOT GA27360 AT calimero DOT vinschen DOT de> <20050505231637 DOT GF15066 AT trixie DOT casa DOT cgf DOT cx> <20050509122753 DOT GC3375 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Corinna Vinschen wrote: > On May 6 02:02, Krzysztof Duleba wrote: > > 150 int issocket () const {return dev.devn == FH_UNIX;} > > (gdb) n > > 78 set_errno (EBADF); > > (gdb) n > > 79 return 0; > > Your debugging shows that my assumption was correct. The file isn't > recognized as socket anymore. This was already shown by `cat' printing > the contents of the socket file, though. The problem is that we still > don't know why, when and by which process the file is changed so that > it's not recognized as socket anymore. More debugging is required. > > You wrote that this happens after 10 minutes, regardless if the socket > is used or not. Does the output of `ls -l' on the file change after > the 10 minutes? What does `ls -l' on the file print anyway? $ ls -l /tmp/.s.PGSQL.5432 srwxrwxrwx 1 SYSTEM Administratorzy 53 May 9 18:21 /tmp/.s.PGSQL.5432 $ sleep 600 $ ls -l /tmp/.s.PGSQL.5432 -rwxrwxrwx 1 SYSTEM Administratorzy 53 May 9 18:31 /tmp/.s.PGSQL.5432 I turned off all non-system apps except for cygserver and postgresql and still the same. How can I provide more debug info? Is it possible to check which processes access or modify the socket file? Regards Krzysztof Duleba -- 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/