MKFIFO(1) BSD General Commands Manual MKFIFO(1)NAME
mkfifo -- make fifos
SYNOPSIS
mkfifo [-m mode] fifo_name ...
DESCRIPTION
The mkfifo utility creates the fifos requested, in the order specified.
The options are as follows:
-m Set the file permission bits of the created fifos to the specified mode, ignoring the umask(2) of the calling process. The mode
argument takes any format that can be specified to the chmod(1) command. If a symbolic mode is specified, the op symbols ``+''
(plus) and ``-'' (hyphen) are interpreted relative to an assumed initial mode of ``a=rw'' (read and write permissions for all).
If the -m option is not specified, fifos are created with mode 0666 modified by the umask(2) of the calling process. The mkfifo utility
requires write permission in the parent directory.
DIAGNOSTICS
The mkfifo utility exits 0 on success, and >0 if an error occurs.
STANDARDS
The mkfifo utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compliant.
SEE ALSO mkdir(1), rm(1), mkfifo(2), mknod(2), mknod(8)HISTORY
The mkfifo command appeared in 4.4BSD.
BSD January 5, 1994 BSD
Check Out this Related Man Page
mkfifo(1M) System Administration Commands mkfifo(1M)NAME
mkfifo - make FIFO special file
SYNOPSIS
/usr/bin/mkfifo [-m mode] path...
DESCRIPTION
The mkfifo utility creates the FIFO special files named by its argument list. The arguments are taken sequentially, in the order specified;
and each FIFO special file is either created completely or, in the case of an error or signal, not created at all.
If errors are encountered in creating one of the special files, mkfifo writes a diagnostic message to the standard error and continues with
the remaining arguments, if any.
The mkfifo utility calls the library routine mkfifo(3C), with the path argument is passed as the path argument from the command line, and
mode is set to the equivalent of a=rw, modified by the current value of the file mode creation mask umask(1).
OPTIONS
The following option is supported:
-m mode Sets the file permission bits of the newly-created FIFO to the specified mode value. The mode option-argument will be the same as
the mode operand defined for the chmod(1) command. In <symbolicmode> strings, the op characters + and - will be interpreted rela-
tive to an assumed initial mode of a=rw.
OPERANDS
The following operand is supported:
file A path name of the FIFO special file to be created.
USAGE
See largefile(5) for the description of the behavior of mkfifo when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes).
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of mkfifo: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 All the specified FIFO special files were created successfully.
>0 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWesu |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO mkfifo(3C), attributes(5), environ(5), largefile(5), standards(5)SunOS 5.10 16 Sep 1996 mkfifo(1M)
Gurus,
I did my research (on google, this site and my local library) but I am *still* lost. I am trying to teach myself about `named pipes` playing around with MKFIFO (Why not?).
(1) It seems MKNOD is reserved to ROOT whereas MKFIFO is accessible to all users. Am I correct? If the answer is... (20 Replies)
I have been busy reading away on devices and filesystems and I am stuck on a particular subject matter.. I'm not understanding the concept behind mknod mkfifo makedev or related commands..
can anyone shed some light on the subject.!
any feedback welcome!
moxxx68 (0 Replies)
Hi, so I've got this program("main") that fork executes another ("user"). These programs communicate through fifos.
One communication is a spawn call, where user passes an executable, main forks and executes it. So, I'm keeping track of all my processes using a task table. After the fork (for... (6 Replies)
For example I am creating a file with 646 mode and then later I changed to 767 mode .after some time I want to see what was the initial permission mode .
Here it's 646.. Can we retrieve this info from anywhere ?
Thanks (1 Reply)
Hi All,
Seeking for your assistance on how to lock the script if it's running? meaning anybody can't run my script while it's running.
Please advise,
Thanks, (8 Replies)