* Set -pf option for both isc-dhcp-server and isc-dhcp-server6 so they
create their pid files in a path that's actually writable. (LP: #985417)
* Also allow read access to the pid file in the apparmor profile,
otherwise only the initial start succeeds. (LP: #1005062)
* On upgrade from dhcp3-server, move /etc/default/dhcp3-server to
/etc/default/isc-dhcp-server. (LP: #1003971)
* On upgrade from dhcp3-relay, remove /etc/default/dhcp3-relay.
(LP: #1005547)
* Try to preseed isc-dhcp-relay with the values from
/etc/default/dhcp3-relay. (LP: #1005547)
-- Stephane Graber <email address hidden> Sun, 27 May 2012 20:41:13 -0400
This bug was fixed in the package isc-dhcp - 4.1.ESV- R4-0ubuntu5. 1
--------------- R4-0ubuntu5. 1) precise-proposed; urgency=low
isc-dhcp (4.1.ESV-
* Set -pf option for both isc-dhcp-server and isc-dhcp-server6 so they dhcp3-server to default/ isc-dhcp- server. (LP: #1003971) dhcp3-relay. default/ dhcp3-relay. (LP: #1005547)
create their pid files in a path that's actually writable. (LP: #985417)
* Also allow read access to the pid file in the apparmor profile,
otherwise only the initial start succeeds. (LP: #1005062)
* On upgrade from dhcp3-server, move /etc/default/
/etc/
* On upgrade from dhcp3-relay, remove /etc/default/
(LP: #1005547)
* Try to preseed isc-dhcp-relay with the values from
/etc/
-- Stephane Graber <email address hidden> Sun, 27 May 2012 20:41:13 -0400