paul@955 | 1 | = Cron Task Scheduler Integration = |
paul@955 | 2 | |
paul@1018 | 3 | The periods defined by recurring events are not all recorded in a user's |
paul@1018 | 4 | free/busy collection if such events recur indefinitely. Instead, only the |
paul@1018 | 5 | periods within a certain window of time are recorded for such events. As a |
paul@1018 | 6 | consequence, free/busy collections need to be progressively expanded over |
paul@1018 | 7 | time to include periods that were ignored when previously recording |
paul@1018 | 8 | free/busy information for an event. |
paul@955 | 9 | |
paul@955 | 10 | The `conf/cron/cron.daily/imip-agent` file contains commands that update |
paul@955 | 11 | free/busy collections for all known users, and this should be copied to the |
paul@955 | 12 | appropriate destination. For example: |
paul@955 | 13 | |
paul@955 | 14 | {{{ |
paul@955 | 15 | cp conf/cron/cron.daily/imip-agent /etc/cron.daily/ |
paul@955 | 16 | }}} |
paul@955 | 17 | |
paul@955 | 18 | Where frequency-specific directories are not supported by cron on a system, a |
paul@955 | 19 | `crontab` entry of the appropriate format is required instead. |
paul@955 | 20 | |
paul@955 | 21 | See the [[../EventRecurrences|guide to event recurrences]] for more information |
paul@955 | 22 | on how recurring events are supported. |
paul@1018 | 23 | |
paul@1018 | 24 | Responsibility for generating free/busy expansions lies with the |
paul@1018 | 25 | `tools/make_freebusy.py` program, which is a general tool that can also |
paul@1018 | 26 | reset the free/busy records defined for a user or those made available to a |
paul@1018 | 27 | user. |