Re: Problems with permissions after CYGWIN upgrade - Mailing list pgsql-cygwin

From David R Robison
Subject Re: Problems with permissions after CYGWIN upgrade
Date
Msg-id 000201c2ee40$e0709f30$0864a8c0@D901K911
Whole thread Raw
In response to Re: Problems with permissions after CYGWIN upgrade  (Jason Tishler <jason@tishler.net>)
Responses Re: Problems with permissions after CYGWIN upgrade
List pgsql-cygwin
If I change the permissions on the files to 777 then it works fine. Any
ideas?

David R Robison
Open Roads Consulting, Inc.
http://www.openroadsconsulting.com


-----Original Message-----
From: Jason Tishler [mailto:jason@tishler.net]
Sent: Wednesday, March 19, 2003 12:44 PM
To: David R Robison
Cc: pgsql-cygwin@postgresql.org
Subject: Re: [CYGWIN] Problems with permissions after CYGWIN upgrade

On Wed, Mar 19, 2003 at 09:29:19AM -0500, David R Robison wrote:
> The file permissions in /tmp are:
>
> total 5512
> drwxrwxrwx+   2 Administ None         4096 Mar 19 08:57 .
> drwxrwxrwx+   9 Administ None         4096 Dec 12 12:59 ..
> -rwx------    1 ???????? None           51 Mar 19 08:57 .s.PGSQL.5432
  ^
  *
> -rw-------    1 ???????? None           31 Mar 19 08:57
.s.PGSQL.5432.lock
> [snip]
>
> Everything use to work file. Any ideas on what might have changed,
> what the problem is, or how to work around it?

I get the following:

    ls -l /tmp/.s.PGSQL.5432*
    srwx------    1 postgres None            0 Mar 19 12:18
/tmp/.s.PGSQL.5432
    -rw-------    1 postgres None           32 Mar 19 12:18
/tmp/.s.PGSQL.5432.lock

It appears that your /tmp/.s.PGSQL.5432 is not considered a socket.
Sorry, but I don't know why.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6


pgsql-cygwin by date:

Previous
From: Jason Tishler
Date:
Subject: Re: Problems with permissions after CYGWIN upgrade
Next
From: Jason Tishler
Date:
Subject: Re: Problems with permissions after CYGWIN upgrade