Report information
The Basics
Id:
46326
Status:
resolved
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
4.4.0 4.3.6+ 4.1-ESV-R15+
Version Found:
4.3.6
Versions Affected:
(no value)
Versions Planned:
4.4.0 4.3.7 4.1-ESV-R16
Priority:
P3 Low
Severity:
S3 Low
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
DHCP Documentation
Area:
bug

Dates
Created:Wed, 18 Oct 2017 21:35:22 -0400
Updated:Tue, 12 Dec 2017 07:44:29 -0500
Closed:Thu, 19 Oct 2017 14:14:05 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

To: dhcp-bugs@isc.org
From: "David H. Gutteridge" <dhgutteridge@sympatico.ca>
Subject: DHCP 4.3.6 - [PATCH] Minor documentation error in dhcpd.8 man page
Date: Thu, 19 Oct 2017 01:35:18 +0000
Bug Report from www.isc.org: Name: David H. Gutteridge Email: dhgutteridge@sympatico.ca Software Version: DHCP 4.3.6 OS: NetBSD Subject:[PATCH] Minor documentation error in dhcpd.8 man page Bug Detail =========== There's a minor documentation error in the dhcpd(8) man page, where an example is missing a semicolon between two parameter statements, which if followed, leads to a configuration file parsing error. --- dhcpd.8.orig 2017-07-25 09:39:54.000000000 -0400 +++ dhcpd.8 2017-10-18 21:31:04.131104855 -0400 @@ -473,7 +473,8 @@ .sp 1 subnet 239.252.197.0 netmask 255.255.255.0 { range 239.252.197.10 239.252.197.250; - default-lease-time 600 max-lease-time 7200; + default-lease-time 600; + max-lease-time 7200; option subnet-mask 255.255.255.0; option broadcast-address 239.252.197.255; option routers 239.252.197.1; --- This email was received through isc.org Bug Submission Form
Hello David: Thank you very much for bringing this to our attention. It's been lurking there for quite some time and it can certainly be annoying to grab a snippet of configuration text that turns out to be wrong. We've corrected this in our upcoming feature release, 4.4.0 due out in Jan '18, and as well as in our maintenance releases 4.3.7/4.1-ESV-R16 whose dates are TBD. Again, thank you for taking the time to submit the issue. We welcome any future submissions you choose to make. Sincerely, Thomas Markwalder ISC Software Engineering