unmerge 502704
reopen 502704
thanks
> > Could you please test with acpid_1.0.6-15? I'd expect it to fix your
> > problem or
> > I misjudged where your problem lies.
> >
> > Michael
>
> Hello.
>
> acpid_1.0.6-15 exhibits the same issue and I confirmed that
> /proc/modules does exist at that point in the script. As a
Sorry, I just reopened the bug.
> As a workaround, I've attached a patch to /etc/init.d/acpid to get past the
> modprobe when it fails. It's a hack but at least it allows acpid to start
> when there are no modules to load. There's likely something bigger at play
> here.
I doubt it. Just running modprobe without any module to load gives a return
code of 1. However, I don't think we should ignore errors but instead check
whether the modules list is empty. How about this:
if [ $MODULES ]; then
modprobe --all --use-blacklist $MODULES 2>/dev/null
fi
Does this work for you?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
