mkfifo(3c) [hpux man page]

mkfifo(3C)																mkfifo(3C)

NAME

       mkfifo() - make a FIFO file

SYNOPSIS

DESCRIPTION

       creates a new FIFO (first-in-first-out) file, at the path name to which path points.  The file permission bits of the new file are initial-
       ized from the mode argument, as modified by the process's file creation mask: for each bit set in the process's file  mode  creation  mask,
       the corresponding bit in the new file's mode is cleared (see umask(2)).	Bits in mode other than the file permission bits are ignored.

       The  FIFO owner ID is set to the process's effective-user-ID.  The FIFO group ID is set to the group ID of the parent directory if the set-
       group-ID bit is set on that directory.  Otherwise the FIFO group ID is set to the process's effective group ID.

       For details of the I/O behavior of pipes see read(2) and write(2).

       The following symbolic constants are defined in the header, and should be used to construct the value of  the  mode  argument.	The  value
       passed should be the bitwise inclusive OR of the desired permissions:

	      Read by owner.
	      Write by owner.
	      Read by group.
	      Write by group.
	      Read by other users.
	      Write by other users.

RETURN VALUE

       returns 0 upon successful completion.  Otherwise, it returns -1, no FIFO is created, and is set to indicate the error.

ERRORS

       fails and the new file is not created if any of the following conditions are encountered:

	      [EACCES]	     A component of the path prefix denies search permission.

	      [EEXIST]	     The named file already exists.

	      [EFAULT]	     The  path	argument  points  outside  the process's allocated address space.  The reliable detection of this error is
			     implementation dependent.

	      [ELOOP]	     Too many symbolic links encountered in translating the path name.

	      [ENAMETOOLONG] The length of the specified path name exceeds bytes, or the length of a component of  the	path  name  exceeds  bytes
			     while is in effect.

	      [ENOENT]	     A component of the path prefix does not exist.

	      [ENOENT]	     The path argument is null.

	      [ENOSPC]	     Not enough space on the file system.

	      [ENOTDIR]      A component of the path prefix is not a directory.

	      [EROFS]	     The directory in which the file is being created is located in a read-only file system.

AUTHOR

       was developed by HP.

SEE ALSO

       chmod(2), mknod(2), pipe(2), stat(2), umask(2), mknod(5), stat(5), thread_safety(5), types(5).

STANDARDS CONFORMANCE

																	mkfifo(3C)

mkdir(2)							System Calls Manual							  mkdir(2)

NAME

       mkdir - make a directory file

SYNOPSIS

DESCRIPTION

       The  system  call creates a new directory file named by path.  The file permission bits of the new directory are initialized from mode, and
       are modified by the process's file mode creation mask.  For each bit set in the process's file mode creation mask, the corresponding bit in
       the new directory's mode is cleared (see umask(2)).

       The  directory's  owner	ID  is set to the process's effective-user-ID.	If the set-group-ID bit of the parent directory is set, the direc-
       tory's group ID is set to the group ID of the parent directory.	Otherwise, the directory's group ID is set  to	the  process's	effective-
       group-ID.  The set-group-ID bit of the new directory is set to the same value as the set-group-ID bit of the parent directory.

       Symbolic  constants  defining the access permission bits are found in the header and are used to construct the argument mode.  The value of
       the argument mode is the bitwise inclusive OR of the values of the desired permissions.

	      Read by owner.
	      Write by owner.
	      Execute (search) by owner.
	      Read by group.
	      Write by group.
	      Execute (search) by group.
	      Read by others (that is, anybody else).
	      Write by others.
	      Execute (search) by others.

   Access Control Lists - HFS File Systems Only
       On HFS file systems implementing access control lists, the directory is created with three base ACL  entries,  corresponding  to  the  file
       access permission bits (see acl(5)).

   Access Control Lists - JFS File Systems Only
       On JFS file systems that support access control lists, optional ACL entries are created corresponding to the parent directory's default ACL
       entries.  Also, the parent directory's default ACL entries are copied as the new directory's default ACL entries (see aclv(5)).

RETURN VALUE

       returns one of the following values:

	      Successful completion.
	      Failure.
		     An error code is stored in

ERRORS

       If fails, no directory is created and is set to one of the following values:

       A component of the path prefix denies search permission.

       The parent directory of the new directory denies write permission.

       User's or group's disk quota block or inode limit
		      has been reached for this file system.

       The named file already exists.

       path	      points outside the process's allocated address space.  The reliable detection of this error is implementation dependent.

       An I/O error occurred while writing to the file system.

       Too many symbolic links are encountered in translating the path name.

       The maximum number of links to the parent directory,
		      would be exceeded.

       The length of the specified path name exceeds
		      bytes, or the length of a component of the path name exceeds bytes while is in effect.

       A component of the path prefix does not exist.

       Not enough space on the file system.

       A component of the path prefix is not a directory.

       The named file resides on a read-only file system.

AUTHOR

       was developed by the University of California, Berkeley.

SEE ALSO

       acl(2), chmod(2), setacl(2), stat(2), umask(2), acl(5), aclv(5), limits(5).

STANDARDS CONFORMANCE

																	  mkdir(2)