Endpoint Administration Guide for UNIX › NIS Configuration › Name Resolution › Name Resolution on a Server: Deadlock

Name Resolution on a Server: Deadlock

CA ControlMinder performs name resolution on a server that includes itself as a client as follows:

1. CA ControlMinder generates a network request to connect to the relevant server.
2. The kernel extension intercepts this request.
3. The kernel extension permits the request because it knows that the request was made internally by the CA ControlMinder process.
4. The NIS or DNS server (which is located on the same station) generates a request to accept the network connection.
5. The kernel extension intercepts this request.
6. The kernel extension knows that a CA ControlMinder process did not make this request. It places this request on the queue of requests awaiting seosd decision.
7. The seosd daemon is now caught in a deadlock. It is waiting for the reply necessary to complete name resolution, but the process that should provide this reply cannot proceed until seosd gives it permission to accept the network connection. The first request generates the second, and creates a deadlock.