Mail Archives: cygwin/2001/07/31/11:02:02
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/
- Raw text -