[SLE] SuSEconfig won't leave /etc/hosts alone !!
Folks, How do I stop SuSEconfig from screwing around with hosts? I'm running 6.3 on a server with two interfaces, eth0 and eth1. eth0 is on the internet and has a real IP address, eth1 is on the internal network and has a private 192.168.* address. The hostname of the system is assigned in hosts to the address associated with eth0, and the internal interface/address has an arbitrary name. But, when ever I run Yast and do something that causes SuSEconfig to kick in, the private network name attached to 192.168.* is discarded and replaced by the hostname. So I end up with the hostname assigned to the addresses for both eth0 and eth1. Grrrrr :-( Can some wise, sage soul tell me how to give SuSEconfig a frontal lobotamy :-) Thanks, John -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
John McNulty wrote:
Folks,
How do I stop SuSEconfig from screwing around with hosts? I'm running 6.3 on a server with two interfaces, eth0 and eth1. eth0 is on the internet and has a real IP address, eth1 is on the internal network and has a private 192.168.* address. The hostname of the system is assigned in hosts to the address associated with eth0, and the internal interface/address has an arbitrary name.
But, when ever I run Yast and do something that causes SuSEconfig to kick in, the private network name attached to 192.168.* is discarded and replaced by the hostname. So I end up with the hostname assigned to the addresses for both eth0 and eth1. Grrrrr :-(
Can some wise, sage soul tell me how to give SuSEconfig a frontal lobotamy :-)
Thanks,
John
Check your /etc/rc.config file. I think you have this option set: # SuSEconfig can do some checks and modifications for /etc/hosts. # If this is not wanted, set the following variable to 'no' (yes, no). CHECK_ETC_HOSTS=yes See ya, Emerald -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
In /etc/rc.config
#
# SuSEconfig can do some checks and modifications for /etc/hosts.
# If this is not wanted, set the following variable to 'no' (yes, no).
#
CHECK_ETC_HOSTS=no
#
# If CHECK_ETC_HOSTS is set to yes, SuSEconfig sorts your
# /etc/hosts. But in some cases this may be unwanted. So here is a
# flag, where you can configure if /etc/hosts should be "beautified".
# (yes/no)
#
BEAUTIFY_ETC_HOSTS=no
Partial lobotomy or maybe just smacking its paws.
HTH,
Jeffrey
Quoting John McNulty
Folks,
How do I stop SuSEconfig from screwing around with hosts? I'm running 6.3 on a server with two interfaces, eth0 and eth1. eth0 is on the internet and has a real IP address, eth1 is on the internal network and has a private 192.168.* address. The hostname of the system is assigned in hosts to the address associated with eth0, and the internal interface/address has an arbitrary name.
But, when ever I run Yast and do something that causes SuSEconfig to kick in, the private network name attached to 192.168.* is discarded and replaced by the hostname. So I end up with the hostname assigned to the addresses for both eth0 and eth1. Grrrrr :-(
Can some wise, sage soul tell me how to give SuSEconfig a frontal lobotamy :-)
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Thanks Jeffrey, and to everyone else who replied too. That did the trick. Cheers, John On Mon, 20 Mar 2000, Jeffrey L . Taylor wrote:
In /etc/rc.config
# # SuSEconfig can do some checks and modifications for /etc/hosts. # If this is not wanted, set the following variable to 'no' (yes, no). # CHECK_ETC_HOSTS=no
# # If CHECK_ETC_HOSTS is set to yes, SuSEconfig sorts your # /etc/hosts. But in some cases this may be unwanted. So here is a # flag, where you can configure if /etc/hosts should be "beautified". # (yes/no) # BEAUTIFY_ETC_HOSTS=no
Partial lobotomy or maybe just smacking its paws.
HTH, Jeffrey
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Try /etc/rc.config... John McNulty wrote:
Folks,
How do I stop SuSEconfig from screwing around with hosts? I'm running 6.3 on a server with two interfaces, eth0 and eth1. eth0 is on the internet and has a real IP address, eth1 is on the internal network and has a private 192.168.* address. The hostname of the system is assigned in hosts to the address associated with eth0, and the internal interface/address has an arbitrary name.
But, when ever I run Yast and do something that causes SuSEconfig to kick in, the private network name attached to 192.168.* is discarded and replaced by the hostname. So I end up with the hostname assigned to the addresses for both eth0 and eth1. Grrrrr :-(
Can some wise, sage soul tell me how to give SuSEconfig a frontal lobotamy :-)
Thanks,
John
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
John McNulty wrote:
Folks,
How do I stop SuSEconfig from screwing around with hosts? I'm running 6.3 on a server with two interfaces, eth0 and eth1. eth0 is on the internet and has a real IP address, eth1 is on the internal network and has a private 192.168.* address. The hostname of the system is assigned in hosts to the address associated with eth0, and the internal interface/address has an arbitrary name.
But, when ever I run Yast and do something that causes SuSEconfig to kick in, the private network name attached to 192.168.* is discarded and replaced by the hostname. So I end up with the hostname assigned to the addresses for both eth0 and eth1. Grrrrr :-(
Can some wise, sage soul tell me how to give SuSEconfig a frontal lobotamy :-)
Thanks,
John
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Try /etc/rc.config -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
dmarkh＠cfl.rr.com -
emy＠emerald.tmfweb.nl -
john＠jmtl.com -
muskrat＠texas.net