Bug 3440
Summary: | pump does not produce the same information that dhcpcd (which it replaces) used to produce. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | dittrich |
Component: | pump | Assignee: | Erik Troan <ewt> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | ||
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: | 2000-02-03 15:47:44 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
dittrich
1999-06-13 22:54:32 UTC
The issues regarding pump are being addressed (read: pump is primitive) but there is no solution as of today (or probably for the next month). Meanwhile, dhcpcd is distributed with Red Hat 6.0 and there is an update that includes the directory in which the file needed by ipchains exists. I'd think seriously abou using dhcpcd if you need a solution today and are unable and/or unwilling to help fix pump. Is using 'pump -s' from your scripts not a good enough way of getting the status information you need? I intended that to include everything your type of application might need. Please let me know what else pump -s should include. ------- Email Received From Dave Dittrich <dittrich.edu> 06/24/99 10:29 ------- ------- Email Received From Erik Troan <ewt> 06/24/99 11:04 ------- ------- Email Received From Dave Dittrich <dittrich.edu> 06/24/99 14:48 ------- If pump -s does not address your needs, please let me know. It should contain the proper information, and we believe it is a reasonable alternative to /etc/dhcpc |