Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ftok(3c) [hpux man page]

ftok(3C)																  ftok(3C)

NAME
ftok() - create interprocess communication identifier SYNOPSIS
DESCRIPTION
All interprocess communication facilities require the user to supply a key to be used by the and system calls to obtain interprocess commu- nication identifiers (see msgget(2), semget(2), and shmget(2)). returns a key based on path and id that is usable in subsequent and system calls. The parameters for the function are as follows: path must be the path name of an existing file that is accessible to the process. id is a character that uniquely identifies a project. This means that only the low order 8-bits of id are signifi- cant. Note that returns the same key for linked files when called with the same id and that it returns differ- ent keys when called with the same file name but different ids. RETURN VALUE
returns if path does not exist or if it is not accessible to the process. EXAMPLES
The following call to returns a key associated with the file myfile and id WARNINGS
If the file whose path is passed to is removed when keys still refer to the file, future calls to with the same path and id will return an error. If the same file is recreated, is likely to return a different key than it did the original time it was called. SEE ALSO
intro(2), msgget(2), semget(2), shmget(2), thread_safety(5). ftok(3C)

Check Out this Related Man Page

ftok(3C)						   Standard C Library Functions 						  ftok(3C)

NAME
ftok - generate an IPC key SYNOPSIS
#include <sys/ipc.h> key_t ftok(const char *path, int id); DESCRIPTION
The ftok() function returns a key based on path and id that is usable in subsequent calls to msgget(2), semget(2) and shmget(2). The path argument must be the pathname of an existing file that the process is able to stat(2). The ftok() function will return the same key value for all paths that name the same file, when called with the same id value, and will return different key values when called with different id values. If the file named by path is removed while still referred to by a key, a call to ftok() with the same path and id returns an error. If the same file is recreated, then a call to ftok() with the same path and id is likely to return a different key. Only the low order 8-bits of id are significant. The behavior of ftok() is unspecified if these bits are 0. RETURN VALUES
Upon successful completion, ftok() returns a key. Otherwise, ftok() returns (key_t)-1 and sets errno to indicate the error. ERRORS
The ftok() function will fail if: EACCES Search permission is denied for a component of the path prefix. ELOOP Too many symbolic links were encountered in resolving path. ENAMETOOLONG The length of the path argument exceeds {PATH_MAX} or a pathname component is longer than {NAME_MAX}. ENOENT A component of path does not name an existing file or path is an empty string. ENOTDIR A component of the path prefix is not a directory. The ftok() function may fail if: ENAMETOOLONG Pathname resolution of a symbolic link produced an intermediate result whose length exceeds {PATH_MAX} . USAGE
For maximum portability, id should be a single-byte character. Another way to compose keys is to include the project ID in the most significant byte and to use the remaining portion as a sequence num- ber. There are many other ways to form keys, but it is necessary for each system to define standards for forming them. If some standard is not adhered to, it will be possible for unrelated processes to unintentionally interfere with each other's operation. It is still possible to interfere intentionally. Therefore, it is strongly suggested that the most significant byte of a key in some sense refer to a project so that keys do not conflict across a given system. NOTES
Since the ftok() function returns a value based on the id given and the file serial number of the file named by path in a type that is no longer large enough to hold all file serial numbers, it may return the same key for paths naming different files on large filesystems. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
msgget(2), semget(2), shmget(2), stat(2), attributes(5), standards(5) SunOS 5.11 24 Jul 2002 ftok(3C)
Man Page