Difference between revisions of "Delays on Update"
Jump to navigation
Jump to search
m |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
* Changes in users' SSH keys take effect immediately. | * Changes in users' SSH keys take effect immediately. | ||
| − | * Updating active project features (creation of requested repositories, etc.) and synchronization of the users' account data, such as project membership, GPG keys, is run each | + | * Updating active project features (creation of requested repositories, etc.) and synchronization of the users' account data, such as project membership, GPG keys, is run each 30 minutes. |
| − | * Creation of | + | * Creation, deletion and reconfiguration of mailing lists is run each 30 minutes: at 05 and 35 minute of each hour. |
* Daily tarballs of existing repositories are created daily at 05:06 EST. | * Daily tarballs of existing repositories are created daily at 05:06 EST. | ||
* [[Project_webpages|Web pages]] are updated 2 seconds after commit. | * [[Project_webpages|Web pages]] are updated 2 seconds after commit. | ||
Latest revision as of 13:45, 11 January 2022
Several functions related to mail aliases, external services access (SVN, CVS...), user additions, group member changes, CVS, etc, are performed via cronjobs on a regular basis.
The exact scheduling is described below:
- Changes in users' SSH keys take effect immediately.
- Updating active project features (creation of requested repositories, etc.) and synchronization of the users' account data, such as project membership, GPG keys, is run each 30 minutes.
- Creation, deletion and reconfiguration of mailing lists is run each 30 minutes: at 05 and 35 minute of each hour.
- Daily tarballs of existing repositories are created daily at 05:06 EST.
- Web pages are updated 2 seconds after commit.