This folder contains crontab files and templates. Crontab define a schedule for automated activities that are executed with the 'crond' scheduler system.
Documentation on the 'crond' scheduler can be found with: man cron
Files here in /p4/common/etc/cron.d should be named like so: crontab.$USER.$(HOSTNAME -s) (or this, which is equivalent: crontab.$(id -n -u).${HOSTNAME%%.*}).
That is, crontab.operating_system_user_id.short_hostname
Sample: crontab.perforce.bos-helix-01
If you are using the 'Tight Ship' style management of the Helix Management System (HMS), the suggested naming convention above is required.
For more information on HMS, see Helix Management System.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 27761 | tom_tyler |
Released SDP 2020.1.27759 (2021/05/07). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #1 | 22685 | russell_jackson | Update main with current changes from dev. | ||
| //guest/perforce_software/sdp/dev/Server/Unix/p4/common/etc/cron.d/ReadMe.md | |||||
| #1 | 22622 | tom_tyler |
Renamed crontab templates files to be template.* rather than *.template.
This is an 'optimize for lazy' tweak, since if we use a prefix, then the actual crontab files named of the form crontab.$USER.${HOSTNAME%%.*} won't have command line completion conficts with the templates. Added a ReadMe.md file describing the suggested (and with HMS required) naming convention for crontab files. Added a command summary doc for the sdp_sync.sh script that manages crontab files in a tight ship deployment. The reference to this file from the ReadMe.md file won't work now with this change in the dev branch, but will work once promoted to main. |
||