|May the source be with you, but remember the KISS principle ;-)|
|Contents||Bulletin||Scripting in shell and Perl||Network troubleshooting||History||Humor|
|News||See Also||Recommended Links||hostname command||/etc/hosts|
|nslookup||dig||Sysadmin Horror Stories||Humor||Etc|
Normally we will set the hostname of a system during the installation process. But if we need to change it after that we are in uncharted territory. For example Red hat by default uses as hostname fully qualified DNS name which for many people including me does not sound as a great idea. In this case you need to find a way to change it to a short name. The problem here is that this name is present in multiple files and generally is Unix/Linux flavour dependent.
While command hostname can change the current hostname, this change is temporary. You can't use the command hostname new_name for permanent changes as hostname command changes only relevant memory structure which would be wiped out after reboot. Also remains unchanged the file /etc/hosts/ that usually contains the association of primary network interface of the box with this name.
Instead of command hostname new_name you can use command sysctl kernel.hostname=new_name or direct write to /proc pseudo filesystem. for example:echo splab02 > /proc/sys/kernel/hostname
You can also print the value /proc/sys/kernel/hostname or use command sysctl kernel.hostname to verify the change.
GNU version of hostname has --file option that provides the opportunity to read the name from the file which is useful in SLES as permanent hostname in SLES is stored in /etc/HOSTNAME. For example:
hostname --file /etc/HOSTNAME
should permanently set the hostname of the system to name you already put in /etc/HOSTNAME. Again this will work only in SLES. Here is a relevant quote from the man page about --file option:
Set NameWhen called with one argument or with the --file option, the commands set the host name, the NIS/YP domain name or the node name.
Note, that only the super-user can change the names.
It is not possible to set the FQDN or the DNS domain name with the dnsdomainname command (see THE FQDN below).
The host name is usually set once at system startup in /etc/rc.d/rc.inet1 or /etc/init.d/boot (normally by reading the contents of a file which contains the host name, e.g. /etc/hostname).
If you issue the command
hostname newnameit is equivalent to writing the specified name into /proc/sys/kernel/hostname so it is important to understand that this is temporary "in-memory-only" change. This change should be active right away and will remain after the system will be rebooted. If after the execution of the command your shell prompt reflects the old host name you probably need either to re-source .profile or (or .bash_profile) or to exit the current shell in order to see the change in your shell prompt.
|If after the execution of the command your shell prompt reflects the old hostname you probably need either to re-source .profile (or .bash_profile) or to exit the current shell in order to see the change in your shell prompt.|
To make the change persistent you still need manually edit two files:
/etc/sysconfig/network in RHEL (/etc/HOSTNAME in SLES)
To check the change you can use either command
hostname -sAgain it is important to understand that the command hostname does not change niether /etc/hosts nor /etc/sysconfig/network in RHEL (/etc/HOSTNAME in SLES) and that should be done manually.
This is the place where hostname in stored in RHEL and its derivatives. As such this is a distribution dependent place and other Linux distributions has thier own way of storing this information. So this is Red Hat and its derivatives (CentOS, Oracle Unbreakable Linux) centric discussion.
For those distributions you can modify the file /etc/sysconfig/network to read the hostname at system boot. This files is sourced by the init script /etc/rc.d/rc.sysinit.
For example in the following /etc/sysconfig/network you need to enter the appropriate name using the HOSTNAME variable.
NETWORKING=yes HOSTNAME="myhost" GATEWAY="192.168.0.1" GATEWAYDEV="eth0" FORWARD_IPV4="yes"
In this example, the new hostname would be myhost
To verify that the value of HOSTNAME parameter was changed correctly use:
Please note that this does not change the current hostname as this is "in-memory" information. It will change hostname only on reboot or anytime /etc/rc.d/rc.sysinit startup script will be re-executed (for example in case of runlevel change). Sometimes the latter can be useful
How do you change the hostname in SLES11? I have normally used the /etc/hostname file and rebooted the server in other distros.
I only notice the way to change it is in yast2 -> network devices -> network settings -> Hostnames
I am looking for where it is stored because I want to write a script to update it (apart of a server deployment process).
Thank you for your time
I hate bumping but I'd really like to know since I can not find anything on google or anywhere else about this.
Put it in /etc/hostname as well as in /etc/hosts
Put it in /etc/hostname as well as in /etc/hosts
I have done that and tried restarting but my hostname does not change unless I change it in yast.
I tried putting it in /etc/hostname and /etc/hosts and then rebooting. Executed "hostname" and it still reported the old one.
Changing it via Yast allowed me to update it right away without having to even reboot, just logout and log back in.
I normaly advice people to use YaST because there are a few places where it should be done and YaST knows them where I always forget one or more.
I rely on YaST now and do not know any more all the places where to go.
Does anybody know if YaST keeps a lof of what it does realy?
Henk van Velden
> Maybe you could try SLES forum, as you can get better response from
> the tech and support team there.
> 'SUSE Linux Enterprise Server (SLES) - NOVELL FORUMS'
Tried it. They never seem to respond over there
Which SLE forum did you post in and when?
The three files to change are /etc/HOSTNAME (note case) and /etc/hosts
against the 127.0.0.2 address and also postfix/main.cf Its also the
fully qualified name (FQDN).
Permanent hostname change on RedHat based systems
RedHat based system use the file /etc/sysconfig/network to read the saved hostname at system boot. This is set using the init script /etc/rc.d/rc.sysinit/etc/sysconfig/network NETWORKING=yes HOSTNAME="plain.domainname.com" GATEWAY="192.168.0.1" GATEWAYDEV="eth0" FORWARD_IPV4="yes"
So in order to preserve your change on system reboot edit this file and enter the appropriate name using the HOSTNAME variable.
Use sysctl to change the hostname
Why would someone need a different method of doing the same thing as above? No idea, but here is anyway: use sysctl to change the variable kernel.hostname:
to read the current hostname, andsysctl kernel.hostname=NEW_HOSTNAME
to change it.
Local hostname and domain name of your server defined in text configuration located in /etc directory.
If you are using Red Hat or Fedora Linux
Use redhat-config-network GUI tool. Type following command and click on DNS tab > Setup hostname and domain name:
On other hand you can edit a text file. Find out and set up the value for HOSTNAME in the file /etc/sysconfig/network:
# vi /etc/sysconfig/network
Where, web is hostname and nixcraft.com is your DNS domain name
The box in your example will have hydrogen.lan as its hostname, not hydrogen.
The only way I know of to have hostname return the short hostname and to have hostname -f return the FQDN, is to use both the mentioned options.
So add HOSTNAME=mybox to /etc/sysconfig/network and add
10.10.10.10 mybox.example.com mybox
to /etc/hosts. I like having hostname and hostname -f return different things. By default, Anaconda sets it up like you have it set up now.
Softpanorama hot topic of the month
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: September 12, 2017