Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 10 May 2005 11:15:37 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: postgresql and sockets Message-ID: <20050510091537.GL3375@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20050503091333.GF25050@calimero.vinschen.de> <20050503131339.GA27360@calimero.vinschen.de> <20050505231637.GF15066@trixie.casa.cgf.cx> <20050509122753.GC3375@calimero.vinschen.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 9 20:45, Krzysztof Duleba wrote: > 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? No more debugging necessary. I found the cause of the problem. At one point the file attributes were not correctly stored for socket files and when postgres touches the socket file (which it does every 5 minutes), the correct file attributes got lost. Especially the system bit got lost, which is important to recognize the file as a socket. I've applied a patch to CVS which will show up in the next developers snapshot on http://cygwin.com/snapshots/ Thanks for reporting and debugging, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.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/