dhcp3-server automatically starts ignoring startup rules on package update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dhcp3 (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
recent security upgrade started dhcp3-server even it was forbidden to start. It caused troubles in local network. As the network-important service it must do status checks if it is allowed to start or not.
more of all - it was a security update so it was installed automatically- at night time, and troubles came in the morning already network-wide
the log
Log started: 2010-01-28 07:46:12
(Reading database ... 199239 files and directories currently installed.)
Preparing to replace dhcp3-server 3.1.1-5ubuntu8.1 (using .../dhcp3-
* Stopping DHCP server dhcpd3
...fail!
Unpacking replacement dhcp3-server ...
Preparing to replace dhcp3-client 3.1.1-5ubuntu8.1 (using .../dhcp3-
Unpacking replacement dhcp3-client ...
Preparing to replace dhcp3-common 3.1.1-5ubuntu8.1 (using .../dhcp3-
Unpacking replacement dhcp3-common ...
Processing triggers for man-db ...
Setting up dhcp3-common (3.1.1-5ubuntu8.2) ...
Setting up dhcp3-server (3.1.1-5ubuntu8.2) ...
* Reloading AppArmor profiles ...
...done.
* Starting DHCP server dhcpd3
...done.
Setting up dhcp3-client (3.1.1-5ubuntu8.2) ...
* Reloading AppArmor profiles ...
...done.
Log ended: 2010-01-28 07:47:02
How did you forbid dhcp3-server to start?