SDP-517
Closed
Please use svcinst to start and stop the Perforce Service.
On Windows our svcinst tool is the only tool which will
wait as long as it takes to start or stop the Perforce
Windows Service. svcinst continually polls the
Service Control Manager for the status of our service
until SCM reports that the service is shut down.
All other Service management tools can timeout waiting for
the SCM to return the response from service. If they do
timeout, and control is returned to the caller prematurely,
SDP might proceed with significant maintenance work such as
swapping database files. This introduces a significant
possibility for data inconsistency or corruption.
We can avoid this by using the svcinst tool. The svcinst
tool is in the Helix Server installer and is installed
next to p4d.exe.
On Windows our svcinst tool is the only tool which will
wait as long as it takes to start or stop the Perforce
Windows Service. svcinst continually polls the
Service Control Manager for the status of our service
until SCM reports that the service is shut down.
All other Service management tools can timeout waiting for
the SCM to return the response from service. If they do
timeout, and control is returned to the caller prematurely,
SDP might proceed with significant maintenance work such as
swapping database files. This introduces a significant
possibility for data inconsistency or corruption.
We can avoid this by using the svcinst tool. The svcinst
tool is in the Helix Server installer and is installed
next to p4d.exe.
- Status
- Closed
- Project
- perforce-software-sdp
- Severity
- A
- Reported By
- brett
- Reported Date
- 5 years ago
- Modified By
- Robert Cowham
- Modified Date
- 4 years ago
- Owned By
- rcowham
- Dev Notes
- This job was once job101933 on a different Helix Core
server. - Component
- core-win
- Type
- Bug
For related discussion, see: https://swarm.workshop.perforce.com/changes/26484#comments