1.1 --- a/docs/wiki/CronIntegration Fri Nov 06 15:19:52 2015 +0100
1.2 +++ b/docs/wiki/CronIntegration Fri Nov 06 16:50:07 2015 +0100
1.3 @@ -1,9 +1,11 @@
1.4 = Cron Task Scheduler Integration =
1.5
1.6 -The periods occupied by recurring events are not expanded beyond a certain
1.7 -window of time by imip-agent. As a consequence, free/busy collections need to
1.8 -be progressively expanded over time to include periods occupied by such events
1.9 -that were not previously recorded in those collections.
1.10 +The periods defined by recurring events are not all recorded in a user's
1.11 +free/busy collection if such events recur indefinitely. Instead, only the
1.12 +periods within a certain window of time are recorded for such events. As a
1.13 +consequence, free/busy collections need to be progressively expanded over
1.14 +time to include periods that were ignored when previously recording
1.15 +free/busy information for an event.
1.16
1.17 The `conf/cron/cron.daily/imip-agent` file contains commands that update
1.18 free/busy collections for all known users, and this should be copied to the
1.19 @@ -18,3 +20,8 @@
1.20
1.21 See the [[../EventRecurrences|guide to event recurrences]] for more information
1.22 on how recurring events are supported.
1.23 +
1.24 +Responsibility for generating free/busy expansions lies with the
1.25 +`tools/make_freebusy.py` program, which is a general tool that can also
1.26 +reset the free/busy records defined for a user or those made available to a
1.27 +user.