|
Bugzilla – Full Text Bug Listing |
| Summary: | if you configure postfix as "No connection", system *cannot complete booting* | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Jon Nelson <jnelson-suse> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | Beta 5 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jon Nelson
2006-03-02 04:48:57 UTC
could you please explain what you exactly changed? During setup/install, I set postfix up with "No connection" (the other chocies being "Permanent" and "Dial up") and went on. After reboot, I notice that when it enters runlevel 3, it hangs on starting postfix. I switched to another VT and found that the postfix init script had issued a 'sleep' (pstree rocks). I checked the postfix init script and searched for 'sleep', and found this:
# waiting for qmgr
while [ -z "$(pidof qmgr)" -a $i -gt 0 ]; do
i=$(( $i - 1 ))
sleep 1
done
in the 'start' section. Obviously, this won't ever succeed and one ends up with a system that will NOT complete booting.
I changed the configuration via yast and rebooted and it's all fine now, but it was pretty annoying, and a less technical user would be completely stumped.
i tried this with beta6 and it works for me. Please try with beta6 if possible (and when its released). reopen when it's still not working for you. |