Endpoint Administration Guide for UNIX › Managing Policy Models › Automatic Rule-based Policy Updates › How the Policy Model Updates Subscribers

How the Policy Model Updates Subscribers

When updating subscribers, the Policy Model performs the following actions:

1. The Policy Model tries to fully qualify subscriber names as they are added or deleted from the Policy Model.
2. The PMDB daemon, sepmdd, attempts to update a subscriber database for the amount of time defined by the token _QD_timeout_.
3. If the maximum time elapses and the daemon does not succeed in updating a subscriber, it skips that particular subscriber and tries to update the remainder of the subscribers on its list.
4. After it completes its first scan of the subscriber list, sepmdd then performs a second scan, in which it tries to update the subscribers that it did not succeed in updating during its first scan. During the second scan, it tries to update a subscriber until the connect system call times out (approximately 90 seconds).

Note: The token _QD_timeout_ may be found in both the seos.ini and pmd.ini files. If the token exists in both files, sepmdd uses the value in the pmd.ini file.

Note: Whenever a PMDB encounters an error while propagating updates to subscribers, the sepmdd daemon creates an entry in the Policy Model error log file. This file, ERROR_LOG by default, is located in the PMDB directory (PMDB Location on Disk, PMDB Location on Disk).