> Problem is whenever I reboot the system the FQDN in hosts keeps
> getting overwritten by DHCP causing sendmail to fail.
> How do I stop DHCP from automatically updating the hostname?

Well, that's easy. The process is spelled out here:

http://opensolaris.org/os/community/...ris_DHCP_setup

with the exception that the procedure noted there for modifying the
net-svc script needs to be modified slightly. (I'm working to get
that page updated with the corrections below, which should happen
shortly.) Here is a paragraph that belongs before the diff listing:

The net-svc script is used to start the svc:/network/service
service at boot time. If you ever want to modify one of the
existing service startup scripts, as in the present case, do not
edit the ones Sun ships. Make a copy, edit it as much as you
need, then modify the start/exec property of the associated
service to point to your changed copy. That way, your changes
won't be overwritten should you install a patch Sun supplies or
upgrade to a newer version of the OS.

To that end, we first show the changes in the modified
(net-svc.local) script:

# cd /lib/svc/method
# diff -c net-svc net-svc.local
*** net-svc Fri Jan 21 15:38:22 2005
--- net-svc.local Sun Jun 12 16:56:06 2005

and here is text that belongs right after that listing:

And then we show how to configure the machine to use the
modified script:

# svccfg -v -s svc:/network/service setprop start/exec = \
astring: '("/lib/svc/method/net-svc.local start")'
# svcadm refresh network/service

Glenn wrote:
>> Problem is whenever I reboot the system the FQDN in hosts keeps
>> getting overwritten by DHCP causing sendmail to fail.
>> How do I stop DHCP from automatically updating the hostname?
>
> Well, that's easy. The process is spelled out here:
>
> http://opensolaris.org/os/community/...ris_DHCP_setup
>
> with the exception that the procedure noted there for modifying the
> net-svc script needs to be modified slightly. (I'm working to get
> that page updated with the corrections below, which should happen
> shortly.) Here is a paragraph that belongs before the diff listing:
>
> The net-svc script is used to start the svc:/network/service
> service at boot time. If you ever want to modify one of the
> existing service startup scripts, as in the present case, do not
> edit the ones Sun ships. Make a copy, edit it as much as you
> need, then modify the start/exec property of the associated
> service to point to your changed copy. That way, your changes
> won't be overwritten should you install a patch Sun supplies or
> upgrade to a newer version of the OS.
>
> To that end, we first show the changes in the modified
> (net-svc.local) script:
>
> # cd /lib/svc/method
> # diff -c net-svc net-svc.local
> *** net-svc Fri Jan 21 15:38:22 2005
> --- net-svc.local Sun Jun 12 16:56:06 2005
>
> and here is text that belongs right after that listing:
>
> And then we show how to configure the machine to use the
> modified script:
>
> # svccfg -v -s svc:/network/service setprop start/exec = \
> astring: '("/lib/svc/method/net-svc.local start")'
> # svcadm refresh network/service
>

Cheers for the information, that's resolved the issue completely.

--
Regards,

JasonB

> Well, that's easy. The process is spelled out here:

HUH ?

> with the exception that the procedure noted there for modifying the
> net-svc script needs to be modified slightly. (I'm working to get

Sorry but I really think you have no idea how things work.

"programs also need access to the FQHN. Fixing this automatically at boot time
required a modification to the net-svc script, to include the FQHN on the same
line as the bare hostname:"


Why on earth mess with system scripts if the only thing you need to do is edit
/etc/default/dhcpagent and then simply tell it *not* to pick up the hostname
from the DHCP server (REQUEST_HOSTNAME = no) ?

As documented in the dhcp(5) manualpage.

--
Groetjes, Peter

..\\ PGP/GPG key: http://www.catslair.org/pubkey.asc

> Problem is whenever I reboot the system the FQDN in hosts keeps getting
> overwritten by DHCP causing sendmail to fail.
>
> How do I stop DHCP from automatically updating the hostname?

Very simple, as described in the dhcp(5) manualpage all you need to do is edit
/etc/default/dhcpagent. If you wish to stop this for all interfaces you just
comment out "REQUEST_HOSTNAME=no" to make this work. If you wish to set this up
for a specific interface only you need to prepend the interface name to this
statement, as described in the file itself. For example
"hme0.REQUEST_HOSTNAME=no".

And finally, if you wish to specificly define what the DHCP agent should and
shouldn't pick up (also configurable for each interface seperatly) you can do
so using the "PARAM_REQUEST_LIST".


Whatever you do, I *strongly* suggest you do not edit system method scripts to
accomplish this. Not only is this very bad practice, it will risk your box
becoming unstable the moment Sun updates those scripts (resulting in them being
overwritten) after which your system falls back to the current situation.

Whoever claims that you need to edit or patch system startup scripts to
accomplish this obviously has no idea what he's doing.


--
Groetjes, Peter

..\\ PGP/GPG key: http://www.catslair.org/pubkey.asc

Lion-O wrote:
>> Problem is whenever I reboot the system the FQDN in hosts keeps getting
>> overwritten by DHCP causing sendmail to fail.
>>
>> How do I stop DHCP from automatically updating the hostname?
>
> Very simple, as described in the dhcp(5) manualpage all you need to do is edit
> /etc/default/dhcpagent. If you wish to stop this for all interfaces you just
> comment out "REQUEST_HOSTNAME=no" to make this work. If you wish to set this up
> for a specific interface only you need to prepend the interface name to this
> statement, as described in the file itself. For example
> "hme0.REQUEST_HOSTNAME=no".
>
> And finally, if you wish to specificly define what the DHCP agent should and
> shouldn't pick up (also configurable for each interface seperatly) you can do
> so using the "PARAM_REQUEST_LIST".
>
>
> Whatever you do, I *strongly* suggest you do not edit system method scripts to
> accomplish this. Not only is this very bad practice, it will risk your box
> becoming unstable the moment Sun updates those scripts (resulting in them being
> overwritten) after which your system falls back to the current situation.
>
> Whoever claims that you need to edit or patch system startup scripts to
> accomplish this obviously has no idea what he's doing.
>
>

Ok, thanks for the update on this, I'll have another look at this later
on today and re-work the changes made based on your recommendations above.

For what it's worth, the server I'm using is a VMWare Image used for
demonstration purposes only, not an actual physical production box.
That said, I also understand that it's better to get into the habit of
using best practice, even in a virtual machine environment.

--
Regards,

JasonB