Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 401543 - sys-power/apcupsd - daemon should start after dhcpcd
Summary: sys-power/apcupsd - daemon should start after dhcpcd
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Diego Elio Pettenò (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-30 16:24 UTC by Thomas Deutschmann (RETIRED)
Modified: 2012-01-30 22:08 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Fixed init apcupsd init script (apcupsd.init.3.patch,223 bytes, text/plain)
2012-01-30 16:24 UTC, Thomas Deutschmann (RETIRED) 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Deutschmann (RETIRED) gentoo-dev 2012-01-30 16:24:14 UTC 
Created attachment 300419 [details]
Fixed init apcupsd init script

I configured apcupsd to use SNMP to connect to an UPS.

I added apcupsd to the default run levels.

The problem is, that apcupsd will be started, before the NIC is up (I am using dhcpcd to configure my NIC). This causes apcupsd to segfault.

I reported the problem to upstream and it is fixed in CVS. But the current fix will just exit apcupsd with an error message instead of a crash... a long term fix should keep apcupsd up and running.

Until this long term fix is available, apcupsd should start *after* dhcpcd to make sure, the NIC is up.

Tested against /usr/portage/sys-power/apcupsd/apcupsd-3.14.10-r1.
Comment 1 SpanKY gentoo-dev 2012-01-30 19:34:47 UTC 
err, the init.d already has "use net".  init.d scripts shouldn't be hardcoding specific dhcp client implementations.
Comment 2 Thomas Deutschmann (RETIRED) gentoo-dev 2012-01-30 20:55:52 UTC 
(In reply to comment #1)
> err, the init.d already has "use net".  init.d scripts shouldn't be hardcoding
> specific dhcp client implementations.

I agree. Thank you for your comment.

My problem seems to be caused by Funtoo's own network configuration. I'll have to confirm and will update this bug report.
Comment 3 Thomas Deutschmann (RETIRED) gentoo-dev 2012-01-30 22:08:08 UTC 
OK, can be closed. Sorry for the noise :)