# The form data below was edited by tom_tyler # 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-442 Status: open Project: perforce-software-sdp Severity: B ReportedBy: robert_cowham ReportedDate: 2019/12/20 05:28:31 ModifiedBy: tom_tyler ModifiedDate: 2020/03/11 15:37:26 OwnedBy: robert_cowham Description: os_tweaks.sh does not permanently disable THP transparent huge pages It only does it for the running system, but on reboot things will be back to previous state. Options include advising the user what to do, or just doing it. Update - this seems to be easiest way to do things: https://askubuntu.com/questions/597372/how-do-i-modify-sys-kernel-mm-transparent-hugepage-enabled/610707#610707 So using sysfsutils package - available for Unbuntu and CentOS and not dependent on systemd vs rc.local. Old way: For example /etc/rc.local can be updated to contain: if test -f /sys/kernel/mm/transparent_hugepage/enabled; then echo never > /sys/kernel/mm/transparent_hugepage/enabled fi But this doesn't work on CentOS 7 for example without turning on rc.local service. https://www.thegeekdiary.com/how-to-execute-scripts-commands-using-etc-rc-d-rc-local-in-centos-rhel-7/ Investigations required perhaps. Also we should update os_tweaks.sh for AWS Linux/Linux 2 DevNotes: Component: setup Type: Bug