Description of problem: lib/rpc_subs.c:create_client() does the following: hints.ai_flags = AI_ADDRCONFIG; hints.ai_family = AF_UNSPEC; hints.ai_socktype = SOCK_DGRAM; but, as far as I can tell, create_client() is supposed to work for both UDP (SOCK_DGRAM) and TCP (SOCK_STRAEM) so having SOCK_DGRAM hard-coded here prevents TCP from working. Suggested change: hints.ai_socktype = 0; Later code in create_client filters the results from getaddrinfo() based on ai_protocol and that appears to be sufficient. As it stands, without this change, automounting of some of our NFS servers doesn't work as they did w/ prior releases of autofs. Version-Release number of selected component (if applicable): autofs-5.0.6-7.fc16 How reproducible: 100% in our environment. Let me know if you need further information.
Sounds fine, I'll make that change.
Created attachment 608097 [details] Patch - fix initialization in rpc create_client() How about we give this a try?
Created attachment 608130 [details] Patch - fix libtirpc name clash And this one.
autofs-5.0.6-8.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/autofs-5.0.6-8.fc16
autofs-5.0.6-8.fc16 works for us. Thank you.
Package autofs-5.0.6-8.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing autofs-5.0.6-8.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-13039/autofs-5.0.6-8.fc16 then log in and leave karma (feedback).
autofs-5.0.6-8.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.