Bug#600465: unblock: freeradius 2.1.10+dfsg-1

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On Sun, 2010-10-17 at 13:45 +0200, Josip Rodin wrote:
> People keep coming to the upstream freeradius-users mailing list asking for
> help with 2.0.4, and they increasingly get funny looks because it's a
> randomly ancient version, by the upstream people's standards.
> 
> Right now we have 2.1.8 in squeeze, and I sense the same scenario will
> unfold, hence this request. This time at least we have roughly the last
> upstream point release before the cutoff date, but at the same time:
[...]
> So hopefully God won't kill any kittens if you just let this one through :)

For a point release, that's not a small diff. :-/  I've tried reviewing
it and while some of it makes a fair amount of sense, I don't know the
product well enough to know whether the rest is fixing important bugs,
or just tinkering.

This, from main/events.c, looks obviously wrong, however:

+       home->zombie_period_start.tv_sec = home->last_packet;
+       home->zombie_period_start.tv_sec = USEC / 2;

Presumably the second tv_sec should be tv_usec.

Regards,

Adam