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