Bug 533323

Summary: Wrong usage of ghn_errno and strerror_r
Product: Red Hat Enterprise Linux 5 Reporter: Ian Kent <ikent>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: ikent, jmoyer, yamato
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: autofs-5.0.1-0.rc2.133.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 483756 Environment:
Last Closed: 2010-03-30 08:37:18 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:
Attachments:
Description Flags
Patch - fix incorrect host name lookup error message none

Description Ian Kent 2009-11-06 05:24:26 UTC 
+++ This bug was initially created as a clone of Bug #483756 +++

Created an attachment (id=330729)
A patch fixing the issue.

Description of problem:

When unexisting host name is given, automount reports following message to log
  automount[2234]: create_udp_client: hostname lookup failed: Operation not permitted

because gethostbyname_r is failed. However, in this case, this message should be
  automount[2234]: create_udp_client: hostname lookup failed: Unknown host

Broken message comes from sterror_r(ghn_errno,...); See the patch for more detail.
  
Version-Release number of selected component (if applicable):

  autofs-5.0.3-36

How reproducible:

 This report is just based on code-reading. So I cannot tell the way. Sorry.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

--- Additional comment from ikent on 2009-02-03 09:50:23 EDT ---

OK, will fix.
Comment 2 Ian Kent 2009-11-25 06:18:16 UTC 
Created attachment 373667 [details]
Patch - fix incorrect host name lookup error message
Comment 7 errata-xmlrpc 2010-03-30 08:37:18 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0265.html