# The form data below was edited by robert_cowham # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: SDP-517 Status: closed Project: perforce-software-sdp Severity: A ReportedBy: brett ReportedDate: 2020/03/30 12:01:34 ModifiedBy: robert_cowham ModifiedDate: 2021/07/16 13:07:40 OwnedBy: rcowham Description: 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. DevNotes: This job was once job101933 on a different Helix Core server. Component: core-win Type: Bug