Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B66C7BB.8000009@ece.gatech.edu>
Date: Tue, 31 Jul 2001 10:59:07 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Markus Hoenicka <Markus DOT Hoenicka AT uth DOT tmc DOT edu>
CC: cygwin AT cygwin DOT com
Subject: Re: cygipc works only for administrator? (2nd attempt)
References: <15205 DOT 58625 DOT 483000 DOT 92379 AT gargle DOT gargle DOT HOWL>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

First, make sure that ipc-daemon is NOT running with the "TightSecurity" 
option (check the registry under 
HKLM/SYSTEM/CurrentControlSet/Service/ipc-daemon/Parameters)

The TightSecurity flag should be off ('0x00000000') to allow wide-open 
access

Also, you might try setting the Debug flag to 0x00000001, and watch the 
voluminous messages in your System Log (don't do this long-term, unless 
you like 100MB logfiles...)  Use EventViewer to looks at the logs.

Make sure to restart the ipc-daemon service after changing its flags.

One trick you can try (if you've got a working sshd on your system) is 
ssh back to localhost as, say, Administrator.  run 'ipc-daemon --debug' 
manually.  In another cygwin shell (user=postgres?) try to run ipctest 
or postgres. (Make sure the ipc-daemon *service* is not running.)

Unfortunately, that's about all I can offer -- debugging tips.  No other 
postgres user has reported problems similar to yours; and at this point, 
I think the ONLY people who use cygipc are postgres users...

--Chuck

Markus Hoenicka wrote:

> [I sent this question Sunday night and got no response. There are just
> too many postgres users and a very active cygipc maintainer on this
> list for not getting a single reply, so I guess it kinda slipped
> through. Please let me try again once more.]
> 
> I've been trying to run postgresql as a daemon, but I failed so far
> due to a problem with shared memory. I've set up the latest cygipc
> release on an NT4 box with a fairly recent (~2 weeks) Cygwin
> installation according to the cygipc README. I run cygipc as a daemon
> under the local system account. This works well and ipctest g|h|s
> works if run as an administrator. If I try the same from any other
> account, ipctest h will fail. I tried this from my postgres account
> which has all the user rights that postgresql needs to run as a daemon
> (it fails all the same from any regular user account). The test output
> reads:
> 
> postgres AT WUTZ ~
> $ ipctest g
> Test v0.03
> PRIVATE msgqueue 0 created
> 
> postgres AT WUTZ ~
> $ ipctest s
> Test v0.03
> semaphore 1 created
> 
> postgres AT WUTZ ~
> $ ipctest h
> Test v0.03
> Unable to create shared memory segment
> shmget : Not enough memory
> shmat return code= -1
> nok
> shmat failed, errno= 22
> 
> postgres AT WUTZ ~
> $
> 
> Apparently some additional access rights are necessary which on my box
> only the administrator account has. The cygcheck output is appended
> below. Any help is appreciated.
> 



--
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/