Thanks for the help everyone (Jason, Igor and Jonathan)
#2 did solve the problem. I have also upgraded the cygwin version to
1.5 which was probably another problem.
Now all I have to do is figure out how to use postgres ;)
Some recommended doc improvements (to prevent questions from people like
me... even though the doc already contains all the needed information)
- for the "net start postmaster" command for NT/XP, it might be nice
mention that "net start" and the services applet can give false
positives to the postmaster process starting successfully. in the
applet, a manual refresh will reveal that it hasn't really been
"started". From the command line "net stop postmaster" will give an
error if it truly didn't start up...
- Mention the uname command in comment 14 as a way to check the cygwin
version. I know that I *should* have remembered this...
- cross referencing bugs to individual commands would also be nice
Jason Tishler wrote:
> Jason,
>
> On Mon, Aug 25, 2003 at 11:30:51AM -0400, Jason House wrote:
>
>>JHOUSE@MM112379-2K ~
>>$ cat /var/log/postmaster.log
>>IpcSemaphoreInitialize: semctl(id=2, 0, SETVAL, 0) failed: Invalid argument
>>LOG: startup process (pid 2548) exited with exit code 1
>>LOG: aborting startup due to startup process failure
>
>
> The above indicates that postmaster did not start up. I have seen
> reports of the above error message before. Unfortunately, I have not
> received definitive confirmation of a solution.
>
> Does the following from the README help?
>
> 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. Note cygipc 2.x automatically removes these
> files during normal shutdown so this issue has been essentially
> obviated.
>
> What PostgreSQL and cygipc versions are you running?
>
> Jason
>