Default dhcpd configuration file should acknowledge /etc/ltsp/dhcpd.conf

Bug #196700 reported by Jonathan Carter
4
Affects Status Importance Assigned to Milestone
dhcp3 (Ubuntu)
Fix Released
Low
Martin Pitt

Bug Description

As a consideration to make Ubuntu LTSP both as easy as possible and to avoid it being too intrusive, the DHCP server has been patched to use /etc/ltsp/dhcpd.conf as a configuration file if it exists, instead of /etc/dhcp3/dhcpd.conf.

This works great, however, administrators are confused by this, and often wonder why their changes to /etc/dhcp3/dhcpd.conf does not take effect.

A solution could be to simply add a comment at the top of /etc/dhcp3/dhcpd.conf file that states:
# Note: dhcp3-server will use /etc/ltsp/dhcpd.conf as its configuration file, if it exists

This way, the current solution would continue working, and less confusion would be caused.

Related branches

Murat Gunes (mgunes)
Changed in dhcp3:
importance: Undecided → Wishlist
Revision history for this message
Martin Pitt (pitti) wrote :

Indeed, I'll do that.

Changed in dhcp3:
assignee: nobody → pitti
importance: Wishlist → Low
status: New → In Progress
Martin Pitt (pitti)
Changed in dhcp3:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dhcp3 - 3.0.6.dfsg-1ubuntu5

---------------
dhcp3 (3.0.6.dfsg-1ubuntu5) hardy; urgency=low

  * debian/dhcpd.conf: Add a warning that /etc/ltsp/dhcpd.conf will be used as
    configuration file if it exists. (LP: #196700)

 -- Martin Pitt <email address hidden> Tue, 11 Mar 2008 10:09:48 +0100

Changed in dhcp3:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.