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 To: cygwin@cygwin.com From: "Krzysztof Duleba" Subject: Re: postgresql and sockets Date: Tue, 10 May 2005 21:45:47 +0200 Lines: 18 Message-ID: References: <20050503091333.GF25050@calimero.vinschen.de> <20050503131339.GA27360@calimero.vinschen.de> <20050505231637.GF15066@trixie.casa.cgf.cx> <20050509122753.GC3375@calimero.vinschen.de> <20050510091537.GL3375@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Corinna Vinschen wrote: > 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/ I've downloaded the snapshot and everything seems fine now. Thanks for fixing that! 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/