Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sethostid(2) [ultrix man page]

gethostid(2)							System Calls Manual						      gethostid(2)

       gethostid, sethostid - get or set the unique identifier of the current host

       hostid = gethostid()
       int hostid;

       int hostid;

       The  system  call  establishes  a 32-bit identifier for the current processor that is intended to be unique among all UNIX systems in exis-
       tence.  This is normally a DARPA Internet address for the local machine.  This call is allowed only to the superuser and is  normally  per-
       formed at boot time.

Return Values
       The system call returns the 32-bit identifier for the current processor.

See Also
       hostid(1), gethostname(2)


Check Out this Related Man Page

GETHOSTID(3)						     Linux Programmer's Manual						      GETHOSTID(3)

gethostid, sethostid - get or set the unique identifier of the current host SYNOPSIS
#include <unistd.h> long gethostid(void); int sethostid(long hostid); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): gethostid(): _BSD_SOURCE || _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED sethostid(): _BSD_SOURCE || (_XOPEN_SOURCE && _XOPEN_SOURCE < 500) DESCRIPTION
gethostid() and sethostid() respectively get or set a unique 32-bit identifier for the current machine. The 32-bit identifier is intended to be unique among all UNIX systems in existence. This normally resembles the Internet address for the local machine, as returned by geth- ostbyname(3), and thus usually never needs to be set. The sethostid() call is restricted to the superuser. RETURN VALUE
gethostid() returns the 32-bit identifier for the current host as set by sethostid(). On success, sethostid() returns 0; on error, -1 is returned, and errno is set to indicate the error. ERRORS
sethostid() can fail with the following errors: EACCES The caller did not have permission to write to the file used to store the host ID. EPERM The calling process's effective user or group ID is not the same as its corresponding real ID. CONFORMING TO
4.2BSD; these functions were dropped in 4.4BSD. SVr4 includes gethostid() but not sethostid(). POSIX.1-2001 specifies gethostid() but not sethostid(). NOTES
In the glibc implementation, the hostid is stored in the file /etc/hostid. (In glibc versions before 2.2, the file /var/adm/hostid was used.) In the glibc implementation, if gethostid() cannot open the file containing the host ID, then it obtains the hostname using gethostname(2), passes that hostname to gethostbyname_r(3) in order to obtain the host's IPv4 address, and returns a value obtained by bit-twiddling the IPv4 address. (This value may not be unique.) BUGS
It is impossible to ensure that the identifier is globally unique. SEE ALSO
hostid(1), gethostbyname(3) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at Linux 2010-09-20 GETHOSTID(3)
Man Page

3 More Discussions You Might Find Interesting

1. Programming

gcc symbol reference error in Solaris

Hi there, Honestly i'm not much of a code guy but i found some short piece of code over the net which i need to compile in my Solaris machine (in order to change my hostid). As far as i read - i need to use the gcc to compile this short text file making it an executable file. My problem is... (0 Replies)
Discussion started by: avisht
0 Replies

2. Solaris

Change Solaris hostid

Hi, I've searched the UNIX forum looking for a simple procedure how to change\control my Solaris server hostid. I did found few threads but all of them either have broken links to all kinds of scripts or not described simply for some UNIX beginers user like me. Can anyone assist me? I... (21 Replies)
Discussion started by: avisht
21 Replies

3. Red Hat

How can I change hostid?

There is no /etc/hostid file. I know that there is no relationship between with MAC address and hostid. There are a lot of scripts on the net but how can I exactly do in my case. :rolleyes: (4 Replies)
Discussion started by: getrue
4 Replies