Summary: | Dhcpcd exits after initializing interface while it should keep running | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alwyn Schoeman <alwyn> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 66472 |
Description
Alwyn Schoeman
2004-08-18 21:30:53 UTC
this usually only happens when something is wrong check your log files to see why dhcpcd bailed does it bail if you run it yourself ? I have figured it out. Whenever the dhcp server doesn't provide a lease period, the dhcpcd client assumes that it is infinite and as such assumes that it will not need to hang around to renew the information, thus exiting. 2 solutions: 1) Document this behaviour and leave it up to the user. 2) Have a default lease period specified in /etc/init.d/net.eth0. (option is -l time_in_seconds) I'm leaning towards 1) as 2) makes decision for the user. Note that this behaviour is relevant when like me you alternate between a fixed network and a wireless one. For me it must be shutdown with -z or when I get to work I sit with my resolv.conf from home. agriffis: perhaps add a small note in conf.d/net right after where it mentions the timeout problem ? if not we can just punt this bug I've documented this behaviour in net.example in CVS Fixed in baselayout-1.11.7-r1 |