# 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. # # 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. Job: SDP-301 Status: closed Project: perforce-software-sdp Severity: B ReportedBy: robert_cowham ReportedDate: 2018/02/21 07:47:26 ModifiedBy: robert_cowham ModifiedDate: 2018/02/21 07:59:02 Description: Crontab spamming emails if configurable track=1 The check is_edge inside set_vars does the following. It seems that when track=1, p4d dumps track info to STDERR which then gets automatically emailed - every 5 minutes for default review daemon! Excerpt from ++ local ServerID=p4-ias-bs ++ local RootDir=/p4/1/root ++ local ServicesData= ++ local EdgeCheck= +++ /p4/1/bin/p4d_1 -r /p4/1/root -J off -L /dev/null -k db.server -jd - +++ grep '@db.server@ @p4-ias-bs@' +++ cut -d @ -f 13 Perforce server info: checkpoint dump --- db.config --- pages in+out+cached 3+0+2 --- locks read/write 1/0 rows get+pos+scan put+del 2+0+0 0+0 --- db.counters --- pages in+out+cached 1+0+1 --- locks read/write 1/0 rows get+pos+scan put+del 0+0+0 0+0 --- db.nameval --- pages in+out+cached 1+0+1 --- locks read/write 1/0 rows get+pos+scan put+del 0+0+0 0+0 --- db.logger --- pages in+out+cached 1+0+1 --- locks read/write 1/0 rows get+pos+scan put+del 0+0+0 0+0 --- db.ldap --- pages in+out+cached 1+0+1 --- locks read/write 1/0 rows get+pos+scan put+del 0+0+0 0+0 DevNotes: Type: Bug