1.1 --- a/docs/wiki/CronIntegration Mon Feb 08 18:46:31 2016 +0100
1.2 +++ b/docs/wiki/CronIntegration Mon Feb 08 20:18:15 2016 +0100
1.3 @@ -1,5 +1,22 @@
1.4 = Cron Task Scheduler Integration =
1.5
1.6 +The `conf/cron/cron.daily/imip-agent` file contains commands that update
1.7 +the following:
1.8 +
1.9 + * Free/busy collections for all known users
1.10 + * Quota records for all known quota groups
1.11 +
1.12 +This file should be copied to the appropriate destination. For example:
1.13 +
1.14 +{{{
1.15 +cp conf/cron/cron.daily/imip-agent /etc/cron.daily/
1.16 +}}}
1.17 +
1.18 +Where frequency-specific directories are not supported by cron on a system, a
1.19 +`crontab` entry of the appropriate format is required instead.
1.20 +
1.21 +== Event Recurrences ==
1.22 +
1.23 The periods defined by recurring events are not all recorded in a user's
1.24 free/busy collection if such events recur indefinitely. Instead, only the
1.25 periods within a certain window of time are recorded for such events. As a
1.26 @@ -7,17 +24,6 @@
1.27 time to include periods that were ignored when previously recording
1.28 free/busy information for an event.
1.29
1.30 -The `conf/cron/cron.daily/imip-agent` file contains commands that update
1.31 -free/busy collections for all known users, and this should be copied to the
1.32 -appropriate destination. For example:
1.33 -
1.34 -{{{
1.35 -cp conf/cron/cron.daily/imip-agent /etc/cron.daily/
1.36 -}}}
1.37 -
1.38 -Where frequency-specific directories are not supported by cron on a system, a
1.39 -`crontab` entry of the appropriate format is required instead.
1.40 -
1.41 See the [[../EventRecurrences|guide to event recurrences]] for more information
1.42 on how recurring events are supported.
1.43
1.44 @@ -25,3 +31,18 @@
1.45 `tools/make_freebusy.py` program, which is a general tool that can also
1.46 reset the free/busy records defined for a user or those made available to a
1.47 user.
1.48 +
1.49 +== Quota Journals ==
1.50 +
1.51 +As events are confirmed for resources, where quotas on resources have been
1.52 +imposed, such quotas will be consumed until eventually exhausted, thus
1.53 +preventing future reservations. By expiring records of past events, quotas
1.54 +can effectively be replenished, allowing reservations to be made for future
1.55 +events.
1.56 +
1.57 +See the [[../Resources|resources guide]] for more information in imposing
1.58 +quotas on groups of resources.
1.59 +
1.60 +Responsibility for updating the quota records lies with the
1.61 +`tools/update_quotas.py` program, which can be used manually to update quota
1.62 +information for the indicated quota groups.