How the Policy Model Updates Subscribers
When updating subscribers, the Policy Model performs the following actions:
capamsc141
When updating subscribers, the Policy Model performs the following actions:
- The Policy Model tries to qualify subscriber names fully as they are added or deleted from the Policy Model.
- The PMDB daemon, sepmdd, attempts to update a subscriber database for the amount of time defined by the tokenQD_timeout.
- If the maximum time elapses and the daemon does not succeed in updating a subscriber, it skips that particular subscriber. The daemon then tries to update the remainder of the subscribers on its list.
- After it completes its first scan of the subscriber list, sepmdd performs a second scan. In the second scan, sepmdd 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).
: 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.: Whenever a PMDB encounters an error while propagating updates to subscribers, the sepmdd daemon creates an entry in the Policy Model error log file (see page ). This file, ERROR_LOG by default, is located in the PMDB directory.