Yea I just found that.

I think I was heading towards "why isn't this in the systems install stuff or
better documented for mobile users" question.

ie, if myname exists, isn't that by definition asking for a supercede-like
behaviour in /etc/dhclient.conf?

also, there doesn't seem to be any install-time stuff to create dhclient.conf
which by default is off in defaults/rc.conf

I'm about to try some reboots to confirm it dtrt for me. If it fixed my sendmail
restart blues I'd be super-peachy happy!

-george


On Mon, 7 Apr 2003 13:27:49 +1000
Luke Mewburn<lukem@netbsd.org> wrote:

> On Mon, Apr 07, 2003 at 01:21:38PM +1000, George Michaelson wrote:
>   |
>   | I have /etc/myname defining my hostname.
>   |
>   | but from the behaviours I see moving from cable at home, IETF and
>   | office, dhclient overrides hostname.
>   |
>   | sleep mode re-wakeup causes re-calls of dhclient on all interfaces
>   | sin the live et. which also seems to make sendmail and related
>   | sname-bound daemons go barfo.
>   |
>   | is this possibly why although I think I have FQDN in my hostname, I
>   | find that at reboot I am getting sendmail hangs "can't find my name"
>   | ?
>   |
>   | Is there a way to make dhclient respect the wired-in name of the
>   | host, but still do interface (re)configs?
>   |
>   | just because a server tells me a name, it doesn't mean I want to use
>   | it!
> 
> Hi George.
> 
> In /etc/dhclient.conf, add:
> 
> 	supersede host-name "my-desired-host-name";
> 
> 
> 
> Luke.


-- 
George Michaelson       |  APNIC
Email: ggm@apnic.net    |  PO Box 2131 Milton QLD 4064
Phone: +61 7 3367 0490  |  Australia
  Fax: +61 7 3367 0482  |  http://www.apnic.net