From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
Description of problem:
I encountered this bug twice and very rare and hard to reproduce the
bug. When boot up Linux, FC freeze at Starting sendmail, the only
solution is to reset the PC, but the worst happens, all FC stuffed up
and need to reinstall all over or else you can't even log in to X.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. After installing FC or after many times using FC test 2
2. At process boot up, sendmail service freeze
3. Freeze at Starting sendmail..
This seems to be a hardware or dns problem.
Yes, it could be my ADSL DHCP modem fault, but if there is some
problems with DNS, at least sendmail service can be abandoned and pass
through. But it didn't and once it did but took 15min.
This problem seems triggerable on FC2. Some system-config-* tool is
leaving networking configuration in a bad state. Investigating further...
Found one way to reproduce this. If your /etc/hosts contains an
invalid IP address associated with your hostname, then this message
appears in /var/log/maillog:
Jun 23 21:22:31 ibmlaptop sendmail: My unqualified host name
(ibmlaptop) unknown; sleeping for retry
Then sendmail sits there forever, preventing system startup. IMHO
preventing startup is unacceptable, so we have two options for this
kind of situation:
1) Modify sendmail to ignore this problem - bad solution.
2) Modify our service startup script to detect this corner case, and
display an error message to console as well as log file and
immediately abort startup.
I see that issue too with rawhide of october 3, but sendmail doesn't
sleep forever, but for a minute. My boot process is first stuck with
smartd, before sendmail is launched as a daemon (smartd sends mails
because of errors on disk). sendmail and sm-client also take time to
Oct 4 09:42:24 chapelle sendmail: My unqualified host name
(chapelle) unknown; sleeping for retry
Oct 4 09:43:24 chapelle sendmail: unable to qualify my own
domain name (chapelle) -- using short name
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
There is a shorter timeout in newer sendmail versions.
Fixed in rawhide.