From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040721 Description of problem: # ypserv -p 4005 Segmentation fault Version-Release number of selected component (if applicable): ypserv-2.12.1-2 How reproducible: Always Steps to Reproduce: 1. ypserv -p 4005 2. 3. Actual Results: segfault Expected Results: ypserv to run in background bound to port 4005. Additional info:
I too have noticed this problem. It prevents the (reliable) use of iptables for filtering ypserv requests. ypxfrd does not seem to suffer from this problem. If it cannot bind to the given port it complains gracefully. ypserv doesn't appear to be even attempting to bind to a port since in debug mode it still dies before producing any output.
This is a duplicate of bug 123158, which I reported to Red Hat more than a month ago. They have not responded yet. Note that although "ypserv -p 4005" segfaults, "ypserv --port 4005" works OK (on RHEL3).
Fixed in ypserv-2.13-5. Thanks for your report. *** This bug has been marked as a duplicate of 134910 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.