Tips for initdb-problem Signal 12 and badcall with ipcs

Hy,

when getting signal 12 errors and initdb fails, there
might be problem with cygwinserver-task.

Mostly you also will also get a "Bad call" when using ipcs.

Possible cause:
Direct Installation of ipc-daemon2 with --install-as-service
instead of using cygserver-config leads to a wrong service-name.

Solution
stop ipc-daemon2 if startet
remove service ipc-daemon2 with --remove-as-service

set CYGWIN=server as an enviroment-variable.
Also add c:\cygwin\bin to the path-variable
(might require a reboot, do so, if unsure).

Start cygserver-config in the bash.
Let the script install cygserver as a service.

Verify the installation in the service-list.
You should have a service: "CYGWIN cygserver".
(notice the difference in the name. When installing
direct --install-as-service the name is ipc-daemon2
or something like that).

Start the service (you might have to delete the semaphore-files
in c:\cygwin/tmp first, if startup fails).

Now, you could try ipcs in a dos box. You should get some
infos about cygserver.

No try initdb. It should run through.

Regards PE