Jason Tishler wrote:
...[snip]...
> Please run the attached program under both the Frank and postgres user
> accounts to confirm or refute the above hypothesis and report back to
> the list.
Confirmed. Here's the output run as both 'Frank' (the admin level
acct) and 'postgres':
______________________________________________________________________
Frank@SEESINK /tmp
$ ./cit
1892 = OpenSemaphore() succeeded
______________________________________________________________________
postgres@SEESINK /tmp
$ ./cit
OpenSemaphore() failed with last error = 2
______________________________________________________________________
Note that if I shutdown CygIPC and run the command from 'Frank', the
results are identical to the 'postgres' results. So yes, indeed, it
looks as if to the 'postgres' user, CygIPC does not exist/is not
responding/cannot be accessed. Now the mother of all questions: why?
Why does it work for you and not for me in XP?
Do you run a vanilla XP config? If not, what changes if any do you
make? I can't think of any apps which would get in the way of this, but
then, I'm not 100% clear on how CygIPC is contacted. And as mentioned,
I've tried running CygIPC AS user 'postgres', and even that did not work.
> BTW, I just thought of a potential workaround. What happens if you run
> ipc-daemon under the postgres account. Does "ipctest s" under postgres
> work? Does initdb work? Remember to delete the /tmp files created by
> ipc-daemon before trying.
As mentioned in my last post, way ahead of you. And yes, I always make
sure when I shutdown CygIPC to delete the /tmp/Multi* files. I've
gotten in that habit over time.