Bug 124263

Summary: generate_modprobe.conf generates modprobe.conf which hangs machine
Product: [Fedora] Fedora Reporter: Peter Hunter <peter.hunter>
Component: module-init-toolsAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-19 18:29:59 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 Peter Hunter 2004-05-25 10:17:50 UTC
The following line in modules.conf:

add probeall ip_conntrack ip_conntrack_irc ip_conntrack_ftp

designed to get irc and ftp connection tracking to load when ip_conntrack does gets 
turned into:

install ip_conntrack /sbin/modprobe ip_conntrack_irc; /sbin/modprobe ip_conntrack_ftp; 
/bin/true

which causes a hang as the system tries again and again to insert these two modules.

Deleting that line and using the configuration file for iptables to load the right modules 
works fine, but this was serious since it stopped my machine from booting - every time I 
got to iptables it hung. I had to boot interactively to fix it.

It would have been nice to have had a big dialogue box on the screen of the installer 
saying something like "Warning - new modprobe setup in modprobe.conf. One has been 
automatically generated for you but is not guaranteed to work!"

Version-Release number of selected component (if applicable):
modutils-2.4.26-16

How reproducible:
Always

Steps to Reproduce:
1. Set up a modules.conf containing the line above
2. Use generate_modprobe.conf
3. Load ip_conntrack
    
Actual Results:  Hang

Comment 1 Bill Nottingham 2005-04-19 18:29:59 UTC
Closing bugs on older, no longer supported releases. Apologies for any lack of
response.

This is unlikely to get fixed outside of the upstream generate-modprobe.conf.