.. _registration server setup/autotasks:

Auto Tasks
==========

There is a number of background jobs that are being performed by the
PBAC-based ``teamdrive`` service.

You can review and manage them via the Registration Server Administration
Console by clicking **Manage Auto Tasks**. See chapter *Managing Auto Tasks*
in the *TeamDrive Registration Server Administration Guide* for details.

The frequency of how often the PBAC will wake up can be changed by editing the
file ``/usr/local/primebase/pbstab``. The ``-i``-Option defines the interval
in seconds. The default value is 10 seconds.

Note that the frequency of the individual tasks can be defined differently, by
changing the task's **Frequency** setting.

.. _registration server setup/autotasks/"send emails"-task:

"Send Emails"-Task
------------------

This process sends out emails generated by the Team Drive Clients (e.g.
device activation or Space invitation messages), which are queued in the
Registration Server's internal email queue.

.. _registration server setup/autotasks/"delete old messages"-task:

"Delete Old Messages"-Task
--------------------------

Messages not retrieved by Clients will be deleted from the Registration
Server's internal message queues after the period defined in the Registration
Server settings ``<InvitationStoragePeriod>`` (e.g. invitations and other client messages,
store-forward invitations) and ``<InvitationStoragePeriodFD>`` (invitations
for future devices) 

See :ref:`registration server settings` and :ref:`teamdrive client <--> server
interaction/messages, invitations & invitation types` for details on these
settings and the various message types.

.. _registration server setup/autotasks/"move store forward messages"-task:

"Move Store Forward Messages"-Task
----------------------------------

Existing users can send out Space invitations to users that do not actually
have an account on this Registration Server yet.

This background task encrypts pending invitations for newly registered users
using the public key of the newly created device and enqueues them in the
regular message queue. The new Client then retrieves the invitation within the
normal poll request interval.

See :ref:`teamdrive client <--> server interaction/messages, invitations &
invitation types/store forward invitation` for details.

.. _registration server setup/autotasks/"delete client ips"-task:

"Delete Client IPs"-Task
------------------------

For privacy/data protection reasons, this task removes the Client IP addresses
from the Devices table according to the value of
``<StoreRegistrationDeviceIPinSeconds>`` as described in :ref:`registration
server settings`.

.. _registration server setup/autotasks/"update regserver-list"-task:

"Update RegServer-List"-Task
----------------------------

If TDNS access is active, this task will poll the TeamDrive Master
Registration Server to retrieve a list of new Registration Servers within the
TDNS network.

Users registered on your Registration Server can only invite users from white
listed Registration Servers to their Spaces.

By default, this will be performed every 12 hours.

The automatic white listing of servers depends on the setting
``<TDNSAutoWhiteList>``.

* If set to ``true``, new Registration Servers will be automatically white
  listed.
* If set to ``false`` you have to approve each Registration Server manually,
  via the **Manage Servers** page of the Administration Console.

.. _registration server setup/autotasks/"cleanup"-task:

"CleanUp"-Task
--------------

If API logging is enabled (the global setting ``APIRequestLogging`` is set to
``True``), each API request is logged in a database table. On a busy server,
these log entries can significantly increase the size of the Registration
Server's database over time.

Enabling this task will remove entries from the API log table, if they are
older than 30 days. This task is disabled by default.

.. _registration server setup/autotasks/"expire licenses"-task:

"Expire Licenses"-Task
----------------------

If you issue licenses with an expiration date (by entering a date in the
**Valid until** field), this task takes care of sending out reminder emails to
the license's user(s), informing them about the upcoming expiration. Once the
expiration date has been reached, the license will be invalidated and the
user's TeamDrive clients will fall back to their default license.