Bug 39626
| Summary: | DHCPD RPM missing file | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Allen Barnett <allen> |
| Component: | dhcp | Assignee: | Elliot Lee <sopwith> |
| Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-07-16 13:36:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Allen Barnett
2001-05-08 12:11:07 UTC
AFAIK, you are expected to configure the daemon properly before starting it. This includes dhcpd.conf and an initial leases database (whether empty or not). The package doesn't ship with a default configuration, so no one would manage to start an incompletely configured dhcpd which might cause network trouble. The init script checks existence of dhcpd.leases because dhcpd would fail to start if that file were not present (see man dhcpd.leases). OK. The dhcpd.leases man page is quite clear about what your responsibilities are for configuring DHCPD. Please consider this bug closed, then. Thanks. |