Misplaced Pages

OMAPI: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 00:24, 13 July 2012 editAbhayakara (talk | contribs)Extended confirmed users761 edits Okay, if this is notable, let's make it more accurate and informative.← Previous edit Revision as of 13:23, 18 July 2012 edit undoAbhayakara (talk | contribs)Extended confirmed users761 edits Oops, forgot to make "nodes" wiki link link to the right page.Next edit →
Line 1: Line 1:
{{Orphan|date=November 2006}} {{Orphan|date=November 2006}}
'''OMAPI''' is an ] that stands for '''Object Management Application Programming Interface'''. It is currently used by ] as an ] to manipulate the internal ] of a running instance of the ISC DHCP ] or ]. Uses on the server include editing registration information for managed ] and controlling the operation of the ]. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client. '''OMAPI''' is an ] that stands for '''Object Management Application Programming Interface'''. It is currently used by ] as an ] to manipulate the internal ] of a running instance of the ISC DHCP ] or ]. Uses on the server include editing registration information for managed ] and controlling the operation of the ]. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.


==References== ==References==

Revision as of 13:23, 18 July 2012

This article is an orphan, as no other articles link to it. Please introduce links to this page from related articles; try the Find link tool for suggestions. (November 2006)

OMAPI is an acronym that stands for Object Management Application Programming Interface. It is currently used by ISC DHCP as an API to manipulate the internal data structure of a running instance of the ISC DHCP server or client. Uses on the server include editing registration information for managed nodes and controlling the operation of the DHCP Failover Protocol. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.

References

Categories: