Bug 7220
| Summary: | RH 6.1 installed system keeps sending bootp messages (pump) | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | elsen |
| Component: | pump | Assignee: | Erik Troan <ewt> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | randy |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-02-24 18:15:13 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: | |||
Is pump configuring your device properly? Does the flooding start immediately on boot? No , the flooding does not start immediately on boot
but after the system is fully up; e.g. after KDE or GNOME
has been launched.
Manual tests with killing and launching pump seems to indicate
that a normal bootp sequence occurs upon invoking pump
then after half a minute or so the flooding starts.
Killing pump again resolves the problem.
Regards,
Marc.
For your information ;following a suggestion from someone
in Dejanews I got my problem solved by replacing by using dhcpcd
instead of pump in the /sbin/ifup script.
Best Regards,
Marc (elsen)
Could you add this to syslog.conf: *.debug /var/log/debug restart syslog, run pump, and send me that file along with your /var/log/messages output after you kill pump? provided info through email. What lease time are you getting? Running pump --status right after "pump" should give you this info. Fixed in recent versions of pump. |
- After installation of a DELL PC with RH6.1 with NFS - kickstart method the system keeps sending bootp messages continuously using the "pump" process. How can I stop this ? I can kill pump of course, but I would like a more fundamental solution. I can see that for instance /etc/pump.conf is not created by default on the system, Thanks for your time. Marc ELSEN (elsen)