Summary: | =net-misc/dhcpcd-5.99.7 random SIGTERM on startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markos Chandras (RETIRED) <hwoarang> |
Component: | [OLD] Core system | Assignee: | William Hubbs <williamh> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | base-system, roy |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Markos Chandras (RETIRED)
2013-06-06 17:01:44 UTC
So something sent dhcpcd a SIGTERM. Sadly dhcpcd doesn't know which PID sent it. I suppose I could code this into a future version. I'll go out on a limb and suggest that the Gentoo network scripts are doing this. I would suggest adding dhcpcd to a runlevel by itself and let it work in peace. Roy I run dhcpcd on the boot runlevel. I have not net.eth* on any runlevel apart from net.lo which is also on the boot runlevel. Should I remove net.lo as well? Hmmmm no, don't remove net.lo You posted a log with dhcpcd-5.99.6. Does 5.99.7 behave the same way? Do you see the same problem with dhcpcd-5.5.x or dhcpcd-5.6.x? (In reply to Roy Marples from comment #3) > Hmmmm no, don't remove net.lo > > You posted a log with dhcpcd-5.99.6. Does 5.99.7 behave the same way? Do you > see the same problem with dhcpcd-5.5.x or dhcpcd-5.6.x? I have 5.99.7 installed, rebooted the box, yet the log says that 5.99.6 is starting. Not sure why... I just downgraded to 5.6.8. I will do a couple of reboots to see if I am able to reproduce it. I am running 5.6.8 since this morning on two separate boxes and everything seems to work fine after multiple reboots. It could be a problem with 5.99.7 or it could have been a temporary problem and caused SIGTERM to be delivered. I am not going to do more tests since these are production systems so feel free to close this bug if you want to. The next dhcpcd release will log the PID where the signal came from, which may or may not assist in debugging this. Thanks. Once the new release is out I will update again Hi Markos, Is this still an issue with 6.0.2? Thanks, William Ok, I'm closing this as worksforme. Markos, if this comes up again with 6.0.5, feel free to reopen. |