Ticket #134 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

debathena-zephyr-config should use Hesiod?

Reported by: broder Owned by:
Priority: low Milestone: Summer 2010 (Lucid Deploy)
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

At some point in the past, the Debian zhm didn't support Hesiod servers. That no longer seems to be the case.

We should find out if all the releases we support can do the Hesiod sloc lookups, and use that if they can.

Alternatively, since /etc/default/zephyr-clients is just shell, we could code the Hesiod lookup into there.

Change History

comment:1 Changed 12 years ago by jdreed

  • Component set to --
  • Milestone set to Summer 2010

comment:2 in reply to: ↑ description Changed 11 years ago by geofft

Replying to broder:

At some point in the past, the Debian zhm didn't support Hesiod servers. That no longer seems to be the case.

We should find out if all the releases we support can do the Hesiod sloc lookups, and use that if they can.

They do now -- the oldest Debian/Ubuntu? upstream version is the 20070719 snapshot, which has this code.

Alternatively, since /etc/default/zephyr-clients is just shell, we could code the Hesiod lookup into there.

Probably a bad idea since you will confuse the debconf code, which will add a new zhm_args= line. See also

# This file is automatically rewritten by the zephyr-clients post-install
# script.  So treat it right.

comment:3 Changed 11 years ago by broder

  • Status changed from new to proposed

r24675, in proposed.

comment:4 Changed 11 years ago by broder

  • Status changed from proposed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.