Problem with "corrupt" lease file

Simon Hobson dhcp1 at
Sun Jul 1 17:25:44 UTC 2007

Niall O'Reilly wrote:

>  > That is ANCIENT, upgrade.

>	Yes, but that may be beside the point.
>	OP's situation, IIUC, is that he has:
>	  - equipment which returns string data containing '#'
>            and following characters,
>	  - a version of dhcpd which happily writes this
>            string to the leases file,
>	  - the same and later versions of dhcpd which
>            can't read the string correctly.
>I believe it's a bug in dhcpd that it would write data to the leases 
>file which it can't read back correctly.  I don't know whether this 
>is still found in the current (3.0.5) release.
>	If not (i.e. it's been fixed), OP's best route would be to migrate 
>to 3.0.5

So your argument is "it looks like a bug, upgrade and see if the 
problem is fixed" ?

Since whatever happens it's going to need an upgrade, the logical 
answer is to upgrade and see if it is fixed - which would remove the 
need to go back over many years of stuff to find out if it was or not.

More information about the dhcp-users mailing list