Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 10 Dec 2002 10:11:46 -0500
From:	Jason Tishler <jason AT tishler DOT net>
Subject:	Re: postgres 7.3 IpcSemaphoreCreate: semget(key=1, num=17,
	03600)failed: Function not implemented
In-reply-to:	<at2nsr$av$1@main.gmane.org>
To:	cygwin AT cygwin DOT com
Mail-followup-to:	cygwin AT cygwin DOT com
Message-id:	<20021210151146.GD1752@tishler.net>
MIME-version:	1.0
User-Agent:	Mutt/1.4i
References:	<269620-22002120816132222 AT M2W031 DOT mail2web DOT com>
	<at0jbi$uha$1 AT main DOT gmane DOT org> <20021209182312 DOT GE1620 AT tishler DOT net>
	<at2nsr$av$1 AT main DOT gmane DOT org>

Dan,

On Mon, Dec 09, 2002 at 07:34:59PM +0100, Dan Holmsand wrote:
> Jason Tishler wrote:
> >On Mon, Dec 09, 2002 at 12:05:16AM +0100, Dan Holmsand wrote:
> >>I get a similar error:
> >>
> >>IpcSemaphoreInitialize: semctl(id=2, 0, SETVAL, 0) failed: Invalid argument
> >
> >The above is noted in the README:
> >
> >    2. It is recommended to delete all cygipc temporary files
> >    (/tmp/cygipc* and /tmp/MultiFile*) before starting postmaster
> >    under a different user account.  Otherwise, postmaster will fail
> >    to start due to IPC errors.
> 
> I know. However, this doesn't necessarily help if ipc-daemon is run by
> one account (say, "system" or "administrator") and postmaster by
> another (say, "postgres").

IMO, the above is not applicable.  I routinely run ipc-daemon under
system (as a service) or myself (i.e., jt) and postmaster under
postgres.  The issue in my README pertains to starting postmaster under
different user accounts.

In my experience, it is the /tmp/cygipc_* files that cause the problem
not the /tmp/MultiFile* files:

    $ ls -l /tmp/cygipc_*
    -rw-------    1 jt       None      1441792 Dec 10 09:56 /tmp/cygipc_0

This is to be expected due to the write-only by owner permissions above.

> In my experience at least, postgres must have read AND write rights to
> the /tmp/MultiFile* files, otherwise you get the above error on
> startup.

On the other hand, I can switch back and forth between running ipc-daemon
as system and any other user because ipc-daemon creates /tmp/MultiFile*
with write by everyone permissions:

    $ ls -l /tmp/MultiFile* 
    -rw-rw-rw-    1 SYSTEM   SYSTEM    3916520 Dec 10 09:56 /tmp/MultiFileMsg
    -rw-rw-rw-    1 SYSTEM   SYSTEM      22032 Dec 10 09:56 /tmp/MultiFileSem
    -rw-rw-rw-    1 SYSTEM   SYSTEM     202768 Dec 10 09:56 /tmp/MultiFileShm

BTW, are you running ipc-daemon with --tight-security?  Maybe this
explains the difference between what we are observing?

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

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -