Bug 439347

Summary: Sendmail hangs on boot
Product: [Fedora] Fedora Reporter: Andre Turpin <andreturpin>
Component: sendmailAssignee: Thomas Woerner <twoerner>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8CC: david
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-21 20:45:12 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 Andre Turpin 2008-03-28 06:42:20 UTC
Description of problem:
Sendmail hangs on install for easily five minutes...argh!

Version-Release number of selected component (if applicable):
Version 8.14.2
 Compiled with: DNSMAP HESIOD HES_GETMAILHOST LDAPMAP LOG MAP_REGEX
                MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6
                NETUNIX NEWDB NIS PIPELINING SASLv2 SCANF SOCKETMAP STARTTLS
                TCPWRAPPERS USERDB USE_LDAP_INIT

How reproducible:
Every boot.


Steps to Reproduce:
1. Reboot laptop (Acer Aspire 5570)
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Thomas Woerner 2008-03-28 09:54:08 UTC
Please check your network configuration altogether with name resolving and the
local host name also with reverse mapping. Your host name should be resolvable
as a full qualified host name.

Comment 2 David Nalley 2008-08-21 20:45:12 UTC
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.