nodename(4) [linux man page]
nodename(4) File Formats nodename(4) NAME
nodename - local source for system name SYNOPSIS
/etc/nodename DESCRIPTION
When a machine is standalone or its IP address is configured locally, the /etc/nodename file contains the system name. By convention, the system name is the same as the hostname associated with the IP address of the primary network interface, for example, hostname.hme0. If the machine's network configuration is delivered by the RPC bootparams protocol, the /etc/nodename file is not used, as the system name is delivered by the remote service. Given a system name value, regardless of source, the uname utility invoked with the -S option is used to set the system name of the running system. If the machine's network configuration is delivered by the DHCP protocol, the /etc/nodename file is used only if the DHCP server does not provide a value for the Hostname option (DHCP standard option code 12). A system name configured in /etc/nodename should be unique within the system's name service domain in order to ensure that any network ser- vices provided by the system will operate correctly. Given a system name value, regardless of source, the uname utility invoked with the -S option is used to set the system name of the running system. EXAMPLES
Example 1: Syntax The syntax for nodename consists of a single line containing the system's name. For example, for a system named myhost: myhost ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
nis+(1), uname(1), named(1M), ypbind(1M), attributes(5) NOTES
The nodename file is modified by Solaris installation and de-installation scripts. SunOS 5.10 9 Feb 2004 nodename(4)
Check Out this Related Man Page
uname(1) General Commands Manual uname(1) NAME
uname - display information about computer system; set node name (system name) SYNOPSIS
nodename] DESCRIPTION
In the first form above, the command displays selected information about the current computer system, derived from the structure (see uname(2)). In the second form, sets the node name (system name) that is used in the structure. Options recognizes the options listed below. If you enter several options, the output is always in the order shown for the option. none Equivalent to Display the options below in the following order, separated by blanks. Display the machine identification number (or the node name, if the machine identification number cannot be determined). This option cannot display the unique machine identification number. For getting the unique machine identification number refer to the command or call. See getconf(1)) and confstr(3C). Display the license level of the operating system. 128-, 256-, and unlimited-user licenses are shown as Display the machine hardware and model names. On Itanium(R)-based systems, this option always displays See Display the node name (system name) by which the system is usually known in a UUCP network. See Display the current release level of the operating system. Display the name of the operating system. On standard HP-UX systems, this option always displays Display the current version level of the operating system. Change the node name (system name) to nodename. nodename is restricted to characters (see uname(2)). See Only users with appropriate privileges can use the option. EXAMPLES
When you execute the command it produces output like the following: The displayed fields are interpreted as follows: The operating system name (option The UUCP network system name by which the system is known The operating system release identifier The operating system version identifier The machine and model numbers The machine identification number The operating system license level WARNINGS
It is recommended that the command or the command be used to obtain the model name, since future model names may not be compatible with See model(1) and getconf(1). Many types of networking services are supported on HP-UX, each of which uses a separately assigned system name and naming convention. To ensure predictable system behavior, it is essential that system names (also called host names or node names) be assigned in such a manner that they do not create conflicts when the various networking facilities interact with each other. The system does not rely on a single system name in a specific location, partly because different services use dissimilar name formats as explained below. The and commands assign system names as follows: +--------------+--------------+---------------+-----------------------+ |Node Name |Command |name Format |Used By | +--------------+--------------+---------------+-----------------------+ |Internet name |hostname name |sys[.x.y.z...] |ARPA and NFS Services | |UUCP name |uname -S name |sys |uucp, related programs | +--------------+--------------+---------------+-------- --------------+ where sys represents the assigned system name. It is recommended that sys be identical for all commands and locations and that the optional follow the specified notation for the particular ARPA/NFS environment. Internet names are also frequently called host names or domain names (which are different from NFS domain names). Refer to hostname(5) for more information about Internet naming conventions. Whenever the system name is changed in any file or by the use of any of the above commands, it should also be changed in all other loca- tions as well. Other files or commands in addition to those above (such as if used to circumvent for example) may contain or alter system names. To ensure correct operation, they should also use the same system name. System names are normally assigned by the script at start-up, and should not be altered elsewhere. Setting a nodename of more than 8 bytes is possible only with the appropriate configuration options enabled. It is strongly recommended that all related documentation be completely understood before setting a larger node name. A node name larger than 8 bytes can cause anomalous or incorrect behavior in applications which use the command or the system function to access the name. SEE ALSO
getconf(1), hostname(1), model(1), setuname(1M), gethostname(2), sethostname(2), uname(2), hostname(5), nodehostnamesize(5). STANDARDS CONFORMANCE
uname(1)