Lines Matching refs:agent

23 Architectural Overview for the DHCP agent
29 The Solaris DHCP agent (dhcpagent) is a DHCP client implementation
40 When a DHCP agent implementation is only required to control a single
42 state-machine, as shown in RFC2131.  However, when a DHCP agent is
51 Indeed, much of the agent's code is there to manage the complexity of
57 The DHCP agent consists of roughly 30 source files, most with a
66 	  the agent; and "async.c", which along with "async.h" defines
68 	  the agent.
70 	* Source files that implement a given state of the agent; for
73 	  REQUESTING state of the agent.  By encapsulating states in
75 	  client/server protocol and adapt the agent to new
90 DHCP agent implementation.  Note that there is of course much more
101 The most important object in the agent is the event handler, whose
104 wrapper around poll(2): other components of the agent can register to
106 instance, to wait for requests to arrive on its IPC socket, the agent
109 associated with the IPC socket.  When the agent initially begins in
112 happen -- this function does not return until the agent is shutdown
119 cannot block, or else the agent will become unresponsive.)
141 are really "singletons".  Accordingly, the agent has two global
148 For each network interface managed by the agent, there is a set of
157 use by the agent.
167 interfaces.  The agent automatically plumbs logical interfaces when
178 nature of the agent requires that functions cannot block, lest they
179 starve out others and impact the observed responsiveness of the agent.
180 As an example, consider the process of extending a lease: the agent
191 callback.  In the agent, the context pointer used depends on the
210 that due to the event-driven model the agent operates in, these
211 operations are not inherently "grouped" -- instead, the agent sends a
218 if while the agent is waiting for an OFFER on a given state machine,
220 agent knows to send back an error since the state machine must be in
223 However, states are not enough -- for instance, suppose that the agent
227 the lease as well, then if the agent were to send another REQUEST,
248 When the agent realizes it must perform an asynchronous transaction,
262 that they may originate from both inside and outside of the agent.
264 he performs an `ifconfig hme0 dhcp start', but the agent will
299 unimportant details away from the rest of the agent code.  In order to