Bug 171936
Summary: | Once started ypbind occupies more and more tcp ports | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Levine <daniel.levine> |
Component: | ypbind | Assignee: | Daniel Riek <riek> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Ben Levenson <benl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cfeist, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-09 21:46:03 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
Daniel Levine
2005-10-27 22:08:32 UTC
Hi, I submitted this a while back. Nothing has happened on this bug report. Is my report or understanding of ypbind deficient? I have a system I really need to run ypbind on that can't run it or it interferes with another program that needs a few ports during network backup. Thanks, Dan NEEDINFO_PM has been deprecated. Changing status to NEEDINFO and changing ownership to pm manager. Does need info mean I haven't provided enough info? If so, I'll be happy to expound upon what have already provided. What do you mean when you say "NIS is gobbling them all up". Are they all in ESTABLISHED state or in TIMEWAIT Most of them appear to be in TIME_WAIT. There are a few in ESTABLISHED. So what does that mean? Or does that mean I'm an idiot? :-) The reason I'm asking was the Arkeia people thought that ypbind was occupying the ports and causing it to have difficulty making its own connections. Is this normal behavior for ypbind clients once they are bound to a yp server? Or is there something interesting going on in my configuration? This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks. Fedora Core 4 is no longer maintained. Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the current Fedora release, please reopen this bug and assign it to the corresponding Fedora version. |