From: Ted Lemon Date: Thu, 5 Sep 1996 23:53:18 +0000 (+0000) Subject: Fix syntax botch in host decl example X-Git-Tag: BETA_5_8~6 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=fc5aedc94f31260cc7aaf82ed2e6d663855e6ec7;p=thirdparty%2Fdhcp.git Fix syntax botch in host decl example --- diff --git a/dhcpd.8 b/dhcpd.8 index 7d04d632a..c0f9aa9a8 100644 --- a/dhcpd.8 +++ b/dhcpd.8 @@ -248,7 +248,8 @@ the server, that file's name must be specified. A simple bootp client declaration might look like this: .nf .sp 1 - host haagen hardware ethernet 08:00:2b:4c:59:23 { + host haagen { + hardware ethernet 08:00:2b:4c:59:23; fixed-address 239.252.197.9; filename "/tftpboot/haagen.boot"; } diff --git a/dhcpd.cat8 b/dhcpd.cat8 index 75a1b4a33..d046e509a 100644 --- a/dhcpd.cat8 +++ b/dhcpd.cat8 @@ -238,7 +238,8 @@ BBOOOOTTPP SSuuppppoorrtt server, that file's name must be specified. A simple bootp client declaration might look like this: - host haagen hardware ethernet 08:00:2b:4c:59:23 { + host haagen { + hardware ethernet 08:00:2b:4c:59:23; fixed-address 239.252.197.9; filename "/tftpboot/haagen.boot"; } @@ -255,7 +256,6 @@ OOppttiioonnss for BOOTP clients, also on a per-client basis. In the event that a BOOTP client declaration specifies options that are also specified in its subnet declaration, the - options specified in the client declaration take @@ -268,8 +268,9 @@ OOppttiioonnss dhcpd(8) dhcpd(8) - precedence. An reasonably complete DHCP configuration - might look something like this: + options specified in the client declaration take prece- + dence. An reasonably complete DHCP configuration might + look something like this: subnet 239.252.197.0 netmask 255.255.255.0 { range 239.252.197.10 239.252.197.250; @@ -324,7 +325,6 @@ AAUUTTHHOORR - 5 diff --git a/server/dhcpd.8 b/server/dhcpd.8 index 7d04d632a..c0f9aa9a8 100644 --- a/server/dhcpd.8 +++ b/server/dhcpd.8 @@ -248,7 +248,8 @@ the server, that file's name must be specified. A simple bootp client declaration might look like this: .nf .sp 1 - host haagen hardware ethernet 08:00:2b:4c:59:23 { + host haagen { + hardware ethernet 08:00:2b:4c:59:23; fixed-address 239.252.197.9; filename "/tftpboot/haagen.boot"; } diff --git a/server/dhcpd.cat8 b/server/dhcpd.cat8 index 75a1b4a33..d046e509a 100644 --- a/server/dhcpd.cat8 +++ b/server/dhcpd.cat8 @@ -238,7 +238,8 @@ BBOOOOTTPP SSuuppppoorrtt server, that file's name must be specified. A simple bootp client declaration might look like this: - host haagen hardware ethernet 08:00:2b:4c:59:23 { + host haagen { + hardware ethernet 08:00:2b:4c:59:23; fixed-address 239.252.197.9; filename "/tftpboot/haagen.boot"; } @@ -255,7 +256,6 @@ OOppttiioonnss for BOOTP clients, also on a per-client basis. In the event that a BOOTP client declaration specifies options that are also specified in its subnet declaration, the - options specified in the client declaration take @@ -268,8 +268,9 @@ OOppttiioonnss dhcpd(8) dhcpd(8) - precedence. An reasonably complete DHCP configuration - might look something like this: + options specified in the client declaration take prece- + dence. An reasonably complete DHCP configuration might + look something like this: subnet 239.252.197.0 netmask 255.255.255.0 { range 239.252.197.10 239.252.197.250; @@ -324,7 +325,6 @@ AAUUTTHHOORR - 5