postgresql and sockets
Corinna Vinschen
corinna-cygwin@cygwin.com
Tue May 10 10:10:00 GMT 2005
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/
More information about the Cygwin
mailing list