imip-agent

docs/wiki/CronIntegration

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