ReadMe.md #1

Crontab Files

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

File Naming Convention

Files here in /p4/common/etc/cron.d should be named like so: crontab.$USER.${HOSTNAME%%.*}

That is, crontab.operating_system_user_id.short_hostname

Sample: crontab.perforce.bos-helix-01

Versioning

If you are using the 'Tight Ship' style mangement of the Server Deployment Package (SDP), the suggested naming convention above is required.

See docs for the sdp_sync.sh script for more information.

For more information, see the tight ship setup script docs.

Crontab Files
===

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```

File Naming Convention
---

Files here in /p4/common/etc/cron.d should be named like so: ```crontab.$USER.${HOSTNAME%%.*}```

That is, crontab.*operating_system_user_id*.*short_hostname*

Sample: crontab.perforce.bos-helix-01

Versioning
---

If you are using the 'Tight Ship' style mangement of the Server Deployment Package (SDP), the suggested naming convention above is required.

See [docs for the sdp_sync.sh script](https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/doc/sdp_sync.command_summary.txt) for more information.

For more information, see [the tight ship setup script docs](https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/doc/hms_ts_setup.command_summary.txt).
# Change User Description Committed
#1 23205 Robert Cowham Merged all changes from dev to test
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/etc/cron.d/ReadMe.md
#1 22622 C. Thomas 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.