bootpc_call() times out
chrisj at rtems.org
Sun Feb 14 00:37:05 UTC 2010
Till Straumann wrote:
> I see that on 2008/05/01 you committed changes (authored by folks at
> mind.be, it seems)
> that let bootpc_call() terminate if no server can be contacted for some
Yes that is correct.
> This is different from pre 4.9 behavior which would keep on trying forever
> until a server replied.
> What was the rationale for this (AFAIK undocumented) change ?
I think networking errors at this protocol level that result in a panic should
be avoided. At a system it is fine to say reboot on a BOOTP error if that is
your requirement but to code into the bootp protocol seem tough on those that
wish to implement a different system level design. For example to try a second
interface or to hand over to a configuration tool that can allow switching to
a different configuration, ie recommissioning equipment.
I know this is not documentation but it was discussed on the list. :)
I will happily change the doco that is wrong. I was not aware the loop
for-ever behaviour was documented. Where is it ?
FYI the retry bootp code never worked because of a bug I fixed in April 2009.
> IMO the old 'forever' loop made more sense.
Can you place the call in a loop ?
More information about the users