summaryrefslogtreecommitdiff
path: root/omapip/omapi.3
diff options
context:
space:
mode:
Diffstat (limited to 'omapip/omapi.3')
-rw-r--r--omapip/omapi.311
1 files changed, 5 insertions, 6 deletions
diff --git a/omapip/omapi.3 b/omapip/omapi.3
index d5de2a61..5edf6275 100644
--- a/omapip/omapi.3
+++ b/omapip/omapi.3
@@ -49,7 +49,7 @@ act as surrogates for the real objects in the server. For example a
client will create a handle for a lease object, and will request the
server to fill the lease handle's state. The client application can
then pull details such as the lease expiration time from the lease
-handle.
+handle.
.PP
Modifications can be made to the server state by creating handles to
new objects, or by modifying attributes of handles to existing
@@ -58,8 +58,8 @@ the changes made.
.SH USAGE
.PP
The client application must always call dhcpctl_initialize() before
-making calls to any other dhcpctl functions. This initializes
-various internal data structures.
+making calls to any other dhcpctl functions. This initializes
+various internal data structures.
.PP
To create the connection to the server the client must use
dhcpctl_connect() function. As well as making the physical connection
@@ -194,7 +194,7 @@ Get the attribute named ``ends'' from the lease handle. This is a
will expire.
.PP
.nf
-
+
memcpy(&thetime, value->value, value->len);
dhcpctl_data_string_dereference(&value, MDL);
@@ -213,7 +213,7 @@ the connection the user must call dhcpctl_new_authenticator.
const char *algorithm = "hmac-md5";
const char *secret = "a-shared-secret";
- dhcpctl_new_authenticator (&authenticator,
+ dhcpctl_new_authenticator (&authenticator,
keyname,
algorithm,
secret,
@@ -246,4 +246,3 @@ dhcpctl(3), omshell(1), dhcpd(8), dhclient(8), dhcpd.conf(5), dhclient.conf(5).
is maintained by ISC. To learn more about Internet Systems Consortium,
see
.B https://www.isc.org
-