1 = Cron Task Scheduler Integration = 2 3 The `conf/cron/cron.daily/imip-agent` file contains commands that update 4 the following: 5 6 * Free/busy collections for all known users 7 * Quota records for all known quota groups 8 9 This file should be copied to the appropriate destination. For example: 10 11 {{{ 12 cp conf/cron/cron.daily/imip-agent /etc/cron.daily/ 13 }}} 14 15 Where frequency-specific directories are not supported by cron on a system, a 16 `crontab` entry of the appropriate format is required instead. 17 18 == Event Recurrences == 19 20 The periods defined by recurring events are not all recorded in a user's 21 free/busy collection if such events recur indefinitely. Instead, only the 22 periods within a certain window of time are recorded for such events. As a 23 consequence, free/busy collections need to be progressively expanded over 24 time to include periods that were ignored when previously recording 25 free/busy information for an event. 26 27 See the [[../EventRecurrences|guide to event recurrences]] for more information 28 on how recurring events are supported. 29 30 Responsibility for generating free/busy expansions lies with the 31 `tools/make_freebusy.py` program, which is a general tool that can also 32 reset the free/busy records defined for a user or those made available to a 33 user. 34 35 == Quota Journals == 36 37 As events are confirmed for resources, where quotas on resources have been 38 imposed, such quotas will be consumed until eventually exhausted, thus 39 preventing future reservations. By expiring records of past events, quotas 40 can effectively be replenished, allowing reservations to be made for future 41 events. 42 43 See the [[../Resources|resources guide]] for more information in imposing 44 quotas on groups of resources. 45 46 Responsibility for updating the quota records lies with the 47 `tools/update_quotas.py` program, which can be used manually to update quota 48 information for the indicated quota groups.