| Lists: | Postg사설 토토SQL |
|---|
| From: | Ian Burrell <ib(at)onsitetech(dot)com> |
|---|---|
| To: | pgsql-cygwin(at)postgresql(dot)org |
| Subject: | Unix sockets permissions problem |
| Date: | 2003-07-18 22:18:38 |
| Message-ID: | 3F18723E.5050801@onsitetech.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
Does anyone know what the problem with the permissions for Unix sockets
with PostgreSQL and Cygwin? The socket file /tmp/.s.PGSQL.5432 is
always created with 700 permissions. This means that it is not
accessible to normal users.
It is possible to change the permissions with the chmod command:
chmod a+rwx /tmp/.s.PGSQL.5432
Is this a bug in Cygwin? Cygipc? PostgreSQL? What needs to be done to
get it fixed?
- Ian
| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Ian Burrell <ib(at)onsitetech(dot)com> |
| Cc: | pgsql-cygwin(at)postgresql(dot)org |
| Subject: | Re: Unix sockets permissions problem |
| Date: | 2003-07-21 07:57:57 |
| Message-ID: | Pine.LNX.4.56.0307210957220.2406@krusty.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | Postg사설 토토SQL |
Ian Burrell writes:
> Does anyone know what the problem with the permissions for Unix sockets
> with PostgreSQL and Cygwin? The socket file /tmp/.s.PGSQL.5432 is
> always created with 700 permissions. This means that it is not
> accessible to normal users.
Change unix_socket_permissions in postgresql.conf (and possibly check the
system umask).
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From: | "Chris Timm" <ctimm(at)primetimetech(dot)com> |
|---|---|
| To: | <pgsql-cygwin(at)postgresql(dot)org> |
| Subject: | Re: Unix sockets permissions problem |
| Date: | 2003-07-21 08:19:42 |
| Message-ID: | 000001c34f60$d7e268e019a8c0@primetimetech.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
Unsubscribe remove
-----Original Message-----
From: pgsql-cygwin-owner(at)postgresql(dot)org
[mailto:pgsql-cygwin-owner(at)postgresql(dot)org] On Behalf Of Peter Eisentraut
Sent: 21 July 2003 08:58
To: Ian Burrell
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: [CYGWIN] Unix sockets permissions problem
Ian Burrell writes:
> Does anyone know what the problem with the permissions for Unix
sockets
> with PostgreSQL and Cygwin? The socket file /tmp/.s.PGSQL.5432 is
> always created with 700 permissions. This means that it is not
> accessible to normal users.
Change unix_socket_permissions in postgresql.conf (and possibly check
the
system umask).
--
Peter Eisentraut peter_e(at)gmx(dot)net
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
| From: | Jason Tishler <jason(at)tishler(dot)net> |
|---|---|
| To: | Ian Burrell <ib(at)onsitetech(dot)com> |
| Cc: | pgsql-cygwin(at)postgresql(dot)org |
| Subject: | Re: Unix sockets permissions problem |
| Date: | 2003-07-21 13:44:51 |
| Message-ID: | 20030721134451.GE1664@tishler.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
Ian,
On Fri, Jul 18, 2003 at 03:18:38PM -0700, Ian Burrell wrote:
> Is this a bug in Cygwin?
Yes.
> What needs to be done to get it fixed?
Upgrade to Cygwin 1.5.0.
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
| From: | Ian Burrell <ib(at)onsitetech(dot)com> |
|---|---|
| To: | pgsql-cygwin(at)postgresql(dot)org |
| Subject: | Re: Unix sockets permissions problem |
| Date: | 2003-07-23 18:13:20 |
| Message-ID: | 3F1ED040.6020709@onsitetech.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-cygwin |
Jason Tishler wrote:
> On Fri, Jul 18, 2003 at 03:18:38PM -0700, Ian Burrell wrote:
>
>>Is this a bug in Cygwin?
>
> Yes.
>
>>What needs to be done to get it fixed?
>
>
> Upgrade to Cygwin 1.5.0.
>
I upgraded to Cygwin 1.5.0 and that fixed the problem. For other
people, Cygwin 1.5.0 is currently marked as experimental. You can
either switch the installer to install experimental packages. Or select
the version of the cygwin package by clicking on it.
- Ian