CServiceConfigData Class Reference
Public Types | |
| typedef std::vector < SC_ACTION > | FailureActions |
Public Member Functions | |
| CServiceConfigData () | |
| void | AddFailureAction (SC_ACTION_TYPE type, JetByteTools::Milliseconds delay) |
| Adds a failure action. There's a hard coded limit of 3 failure actions in the function but this is purely because it's hard to manage services using the services control snap-in if you have more than 3 failure actions. The upper limit is actually somewhere around 900. You can comment the lower limit out if you actually DO require more than 3 failure actions. Although the delay is specified and stored in ms the service control snap-in displays in hours and rounds down to the nearest hour. | |
| const FailureActions & | GetFailureActions () const |
| bool | FailureRequiresRestart () const |
| Returns true if any of the failure actions are SC_ACTION_RESTART. | |
| bool | FailureRequiresReboot () const |
| Returns true if any of the failure actions are SC_ACTION_REBOOT, if so the account doing the installation requires the SE_SHUTDOWN_NAME privilege. | |
Public Attributes | |
| JetByteTools::Core::_tstring | displayName |
| JetByteTools::Core::_tstring | description |
| JetByteTools::Core::_tstring | dependencies |
| ServiceTypes::StartupType | startupType |
| ServiceTypes::ErrorHandling | errorHandling |
| bool | interactive |
| bool | supportsPerformanceCounters |
| DWORD | controlsAccepted |
| DWORD | preShutdownTimeout |
| JetByteTools::Core::_tstring | accountName |
| JetByteTools::Core::_tstring | password |
| JetByteTools::Core::_tstring | requiredPrivileges |
| ServiceTypes::ServiceSIDTypes | serviceSID |
| bool | enableFailureActions |
| JetByteTools::Seconds | failureActionResetPeriod |
| How long the service must be running successfully for the failure count to be reset. Although this is specified in seconds the services control snap-in only displays in days and rounds down to the nearest day. | |
| JetByteTools::Core::_tstring | failureActionRebootMessage |
| JetByteTools::Core::_tstring | failureActionCommandLine |
| bool | serviceFailureActionsOnNonCrash |
Member Typedef Documentation
| typedef std::vector<SC_ACTION> FailureActions |
Constructor & Destructor Documentation
Member Function Documentation
| void AddFailureAction | ( | SC_ACTION_TYPE | type, | |
| JetByteTools::Milliseconds | delay | |||
| ) |
Adds a failure action. There's a hard coded limit of 3 failure actions in the function but this is purely because it's hard to manage services using the services control snap-in if you have more than 3 failure actions. The upper limit is actually somewhere around 900. You can comment the lower limit out if you actually DO require more than 3 failure actions. Although the delay is specified and stored in ms the service control snap-in displays in hours and rounds down to the nearest hour.
| const CServiceConfigData::FailureActions & GetFailureActions | ( | ) | const |
| bool FailureRequiresRestart | ( | ) | const |
Returns true if any of the failure actions are SC_ACTION_RESTART.
| bool FailureRequiresReboot | ( | ) | const |
Returns true if any of the failure actions are SC_ACTION_REBOOT, if so the account doing the installation requires the SE_SHUTDOWN_NAME privilege.
Member Data Documentation
How long the service must be running successfully for the failure count to be reset. Although this is specified in seconds the services control snap-in only displays in days and rounds down to the nearest day.
