Re: Initdb fails - semctl invalid argument

7.4.2 on cygwin is not supported yet and won't be until cygwin version 1.5.10 is released some time this year from what
Iunderstand.  There was an earlier post from Jason Tishler I believe that outlined why 7.4.2 won't work with cygwin
1.5.9

If 7.4.1 doesn't have the same problem with shutting down unexpectedly as 7.4.1-3 does go with that one if you can't
waitfor 1.5.10 to be released. 


On Mon, May 17, 2004 at 11:17:11AM -0600, Rattan, Neeta S wrote:
> Did anyone find a solution to the problem Eric posted below-
> Semctl(17, 16, SETVAL, 536) failed: Invalid argument.
> The solution posted of rebooting the machine did not work for me, and I
> continue to see this problem everytime I try to run initdb (on WinXP,
> cygwin, 7.4.2) with the first argument of semctl increasing on each
> subsequent attempt.
> Please advise!
> -Neeta Rattan
>
> We are getting this same exact error-- always this
>
> semctl(35, 16, SETVAL, 536) failed: Invalid argument
>
> on the creating template1 step of initdb.
>
> On my Windows XP machine I had 7.4.1 working fine last month (service
> configuration).
>
> If I install 7.4.2 I get this error. If I reinstall 7.4.1 (rerun make
> install) initdb works. If I reinstall 7.4.2 it fails again with that semctl
> error. I tried rebuilding 7.41 from scratch and installing, thinking maybe
> it was a configuration difference when I built it last month, but no, 7.4.1
> initdb still works.
>
> My coworker, on the other hand (not running it as a service), gets this same
> semctl error even with 7.4.1.
>
> This is preventing us from switching from mySQL to Postgres. Can anyone
> please offer a clue how to get around this?
>
> Eric Schwarzenbach
>
>