win32_start_service_ctrl_dispatcher
(PECL win32service >=0.1.0)
win32_start_service_ctrl_dispatcher — Registers the script with the SCM, so that it can act as the service with the given name
Description
win32_start_service_ctrl_dispatcher(
string $name
,
bool $gracefulMode
= true):
void
Once started, the service process should do 2 things. The first is to tell
the Service Control Manager that the service is running. This is achieved
by calling win32_set_service_status() with the
WIN32_SERVICE_RUNNING
constant. If you need to perform
some lengthy process before the service is actually running, then you can
use the WIN32_SERVICE_START_PENDING
constant. The
second is to continue to check-in with the service control manager so that
it can determine if it should terminate. This is achieved by periodically
calling win32_get_last_control_message() and handling the
return code appropriately.
Caution
Since version 0.2.0, this function work only in "cli" SAPI. On other SAPI
this function is disabled.
Return Values
No value is returned.
Prior to version 1.0.0, returned WIN32_NO_ERROR
on success, false
if there is a problem with the parameters or a Win32 Error Code on failure.
Errors/Exceptions
Prior to version 1.0.0, if the SAPI is not "cli"
, this function emits an
E_ERROR
level error.
As of version 1.0.0, will throw a
Win32ServiceException if SAPI is not
"cli"
Examples
Example #1 A win32_start_service_ctrl_dispatcher() example
Check if the service is runnig under the SCM.
<?php
if (!win32_start_service_ctrl_dispatcher('dummyphp')) {
die("I'm probably not running under the service control manager");
}
win32_set_service_status(WIN32_SERVICE_START_PENDING);
// Some lengthy process to get this service up and running.
win32_set_service_status(WIN32_SERVICE_RUNNING);
while (WIN32_SERVICE_CONTROL_STOP != win32_get_last_control_message()) {
# do some work here, trying not to take more than around 30 seconds
# before coming back into the loop again
}
?>