| Summary: | sys-power/apcupsd - daemon should start after dhcpcd | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Deutschmann (RETIRED) <whissi> |
| Component: | [OLD] Core system | Assignee: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | base-system |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Fixed init apcupsd init script | ||
err, the init.d already has "use net". init.d scripts shouldn't be hardcoding specific dhcp client implementations. (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. OK, can be closed. Sorry for the noise :) |
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.