First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 158814
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Christian Heim (RETIRED) <phreak@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Magnus Ahlberg <magnus.ahlberg@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 158814 depends on: Show dependency tree
Bug 158814 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-12-22 01:59 0000
When trying to get the new ipw3945d-1.7.22-r4 working correctly I once ran
"modprobe ipw3945" and got the following message:

 * The pidfile (/var/run/ipw3945d/ipw3945d.pid) is still present.
 * Please check that the daemon isn't running!
 * DO NOT USE EXIT IN INIT.D SCRIPTS
 * This IS a bug, please fix your broken init.d
FATAL: Error running install command for ipw3945

And sure enough, the /etc/init.d/ipw3945d init-script uses "exit 1" in it's
check-function, I'm guessing that this should be changed to "return 1" or
something?

------- Comment #1 From Christian Heim (RETIRED) 2006-12-22 02:14:04 0000 -------
(In reply to comment #0)
> When trying to get the new ipw3945d-1.7.22-r4 working correctly I once ran
> "modprobe ipw3945" and got the following message:
> 
>  * The pidfile (/var/run/ipw3945d/ipw3945d.pid) is still present.
>  * Please check that the daemon isn't running!
>  * DO NOT USE EXIT IN INIT.D SCRIPTS
>  * This IS a bug, please fix your broken init.d
> FATAL: Error running install command for ipw3945
> 
> And sure enough, the /etc/init.d/ipw3945d init-script uses "exit 1" in it's
> check-function, I'm guessing that this should be changed to "return 1" or
> something?
> 

You are right, I didn't knew using `exit 1' is forbidden nowadays inside the
init-script when I wrote the init.d file. Thanks to you, it should be fixed
now. Will be on the mirrors on the next sync.

First Last Prev Next    No search results available      Search page      Enter new bug