Bug 154602 - if you configure postfix as "No connection", system *cannot complete booting*
Summary: if you configure postfix as "No connection", system *cannot complete booting*
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 5
Hardware: i686 Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-02 04:48 UTC by Jon Nelson
Modified: 2006-03-03 11:16 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Nelson 2006-03-02 04:48:57 UTC
if you configure postfix as "No connection", system *cannot complete booting* because it stops with the postfix init script which enters a (seeming) infinite loop.
Comment 1 Martin Lasarsch 2006-03-02 13:25:01 UTC
could you please explain what you exactly changed?
Comment 2 Jon Nelson 2006-03-02 15:17:39 UTC
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.

Comment 3 Martin Lasarsch 2006-03-02 15:41:10 UTC
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.