kclient version 2 [PSARC/2007/401 FastTrack timeout 07/13/2007]

[James Carlson]

Wyllys Ingersoll writes:
> -t: configure a simple broadcast/multicast NTP client

Why is this part of kclient?  Though having a tool to administer NTP
clients would probably be helpful (and having it tied into something
like DHCP and thus automatic would be much more helpful still), it
seems out of place here.

> -T kdc_vendor: specify the KDC of the client to be of kdc_vendor.  Supported
> vendors are currently:
> 	ms_ad: Microsoft Active Directory
> 	mit: MIT KDC server
> 	heimdal: Heimdal KDC server
> 	shishi: Shishi KDC server

Why does the user have to specify this?  Is there no way for the
client implementation to detect the proper KDC variant to use?

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677