Upgrade from 3.1.0 to 4.1.1

Abu Abdulla alhanbali montaqa at gmail.com
Sun Feb 21 06:48:22 UTC 2010

> No problem to compile while it's running. If you install the new binary
> over the top of the running executable there may be problems. Not sure
> what your policy is, but I always install into a version-specific
> directory, then symlink to common directory. Otherwise shutdown the old
> one, install and then start.
>>/  - My upgrade procedure will be as follow:
> />/     - Stop the secondary server and copy the lease file
> />/     - Start the new version in the secondary while the primary is still
> />/  running with the old version. i think the failover protocol is still the
> />/  same in these two versions.
> />/     - Stop the primary server and restart it again with the new version.
> /
> Probably safer to stop both servers, then start the new versions. I've
> always been wary of running different versions of the server in
> failover, even when they allegedly use the same protocol. There are a
> lot of bug fixes between 3.1.0 and 4.1.1.

Thanks glenn, i did that and the upgrade went smoothly.

> The raw sockets interface means you can't have two dhcpd processes on
> the same interface. If you compile with USE_SOCKETS (and the limitations
> that currently come with that) then you should be able to do it.

where can i found info on how to compile with USE_SOCKETS and how can
i use this feature. i only need to run multiple DHCP instances on
different ports using the same IP

More information about the dhcp-users mailing list