[En-Nut-Discussion] Possible race condition in DHCP and DHCPKick
hmnews at proconx.com
Tue Feb 14 05:30:38 CET 2012
I thought about a redesign myself, but commercial pressure to get a
project out of the door prohibits this at the moment. So I will apply
only those fixes at the moment and see if more issues pop up.
On 13/02/2012 4:00 AM, Ole Reinhardt wrote:
>> Isn't it more reliably to redesign dhcp into an active and a passive
>> part. The active part can work with post/wait and simply offers a
>> current_state variable like dhcpState.
>> If DHCP_BOUND or DHCP_TOUT is reached it goes to sleep and wait for a
> Good Idea! Please go ahead! (Or your college :)
> I just looked over the code without taking a redesign into account. As
> the DHCP part made several problems in the past a redesign might be the
> better choice.
More information about the En-Nut-Discussion