I've got a system here with a not-fully-supported RTC (sparc64 SunFire
V100) and the end result raises the question of how dhclient might be
fixed to set the time and perhaps do other useful related configuration
tasks when ntp-servers and/or time-servers options are given in the
lease.  Indeed as you can see in this example there are a plethora of
useful options that dhclient seems to completely ignore.

# date                         
Sat Sep 26 23:56:22 EDT 1970
# cat /var/db/dhclient.leases                                                  
lease {
  interface "tlp0";
  fixed-address 204.92.254.135;
  option font-servers 204.92.254.2;			# <<<<
  option x-display-manager 204.92.254.2;		# <<<<
  option subnet-mask 255.255.255.0;
  option routers 204.92.254.6;
  option dhcp-lease-time 36000;
  option time-servers 204.92.254.2;			# <<<<
  option dhcp-message-type 5;
  option domain-name-servers 204.92.254.2,204.92.254.5;
  option dhcp-server-identifier 204.92.254.2;
  option log-servers 204.92.254.2;			# <<<<
  option lpr-servers 204.92.254.2;			# <<<<
  option dhcp-renewal-time 18000;
  option ntp-servers 204.92.254.2;			# <<<<
  option broadcast-address 204.92.254.255;
  option dhcp-rebinding-time 31500;
  option domain-name "weird.com";
  renew 0 1970/9/27 08:04:02;
  rebind 0 1970/9/27 11:56:29;
  expire 0 1970/9/27 13:11:29;
}
# 

There are probably even more that I didn't find interesting at the time
when I configured my DHCP server.

Any suggestions on what the best way to proceed is?  Should I just hack
the scripts dhclient runs to try to make them do something useful with
these options?

Is this something that should be fed back through ISC, or are such
features too platform dependent to worry about going that route?

-- 
								Greg A. Woods

+1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>