Service Control Manager semaphore name problem
Ben A L Jemmett
ben.jemmett at ukonline.co.uk
Thu Oct 9 15:38:35 CDT 2003
Spotted what looks like a simple mistake in the Services code when trying to
get a client's service to run -- it was failing with "Couldn't find wait
semaphore". The semaphore name being used in StartServiceCtrlDispatcherA
had a 'ADVAPI32_' prefix rather than the 'ADVAPI_' used elsewhere in the file.
Changed semaphore name in StartServiceCtrlDispatcherA to match that used
when creating the object in StartServiceW.
RCS file: /home/wine/wine/dlls/advapi32/service.c,v
retrieving revision 1.38
diff -r1.38 service.c
< wait = OpenSemaphoreA(SEMAPHORE_ALL_ACCESS, FALSE, "ADVAPI32_ServiceStartData");
> wait = OpenSemaphoreA(SEMAPHORE_ALL_ACCESS, FALSE, "ADVAPI_ServiceStartData");
Ben A L Jemmett.
More information about the wine-patches