# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1446825007 -3600
# Node ID f1a7fa322894f92e4e75541ab1fd00327d4fc50e
# Parent  722d76350a8544612acab8d4bbecaf35e74b05f9
Tidied up the description of the free/busy expansion mechanism, adding details
of the tool responsible for the work.

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