06-30-2009
Can FIFO file overfow?
I want to output logger information into FIFO file. My application can run for months. My question is what happens to FIFO file when there is one side constantly writing to it and nobody on the other side reading from it?
Will it eventually stuck, overflow, reset, will it take all OS's RAM?
Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All
L2000-44
HP-UX 11.00
I am attempting to setup a FIFO over NFS. Directing and reading from the FIFO works fine on the local machine - however when I direct to the FIFO from a server which has the directory NFS mounted it does not work. The a process to read from the FIFO on the local... (2 Replies)
Discussion started by: saabir
2 Replies
2. Programming
hello i am making a client server program
that communicates via FIFOS and i cannot get it to not hang
i also am forking exec-ing the client from the server
my logic (i will spare you the code )
in the server
i make two fifos in my server my file permissions
are 0644
i then open both... (1 Reply)
Discussion started by: runawayNinja
1 Replies
3. Programming
hi, I have a problem. I've done a lil program which gets from the server the given persons username a personal folder. I made it with a pipe calling popen with a command, but how can i make the same thing using fifo. I make the fifo with mkfifo() func. and than what. How do I tell the sertver using... (3 Replies)
Discussion started by: atticus
3 Replies
4. UNIX for Dummies Questions & Answers
Hi ,
I m beginner for Unix and i want to use FIFO in my 2 Scripts . I want 1 script to read data from FIFO and other will write into FIFO.
Despite reading so many articles/posts i am still unable sunchronize my scripts.
My doubts are
1> Do We require both scripts as daemons to use... (0 Replies)
Discussion started by: Akshay
0 Replies
5. Programming
Hello,
I have a FIFO which i would like to open O_WDWR | O_NONBLOCK | O_ASYNC and have a SIGIO signal generated when there is input on the FIFO, but there a re a bunch of bugs surrounding this (like for instance i read somewhere that you have to set O_ASYNC with fcntl etc.
is this even... (0 Replies)
Discussion started by: davo666
0 Replies
6. Programming
hi, my problem is
i have 10 thread for produces double two dimensional array these will produces 2d array 400 times ,then i have a thread to takes a two dimensional array then it inverse , and most 10 array can be in the fifo , and threads given takes one by one, now my problem is , i cant... (0 Replies)
Discussion started by: bblackened
0 Replies
7. Programming
Hello C programming fellows!!!
I'm doing a program with multiple threads in gnu/linux, ubuntu for beeing precise...
This program consist in multiple threads, as logical each thread do different things and communicate to each other using IPC.
The problem is that in "process 1" I have a... (1 Reply)
Discussion started by: Sandia_man
1 Replies
8. Programming
Dear friends
i'm want to implement a program which one file is split into fragments by the server (by some random size) and sent to some processes, so these processes get randomly the fragments of the original file from the server, then the downloader randomly connects to some of these processes... (0 Replies)
Discussion started by: saman_glorious
0 Replies
9. UNIX and Linux Applications
Hello ,
I am working on unix FIFO IPC. i have a doubt regarding that.
If the fifo is updated(write()) through one process....can we able to send any signal that fifo is updated and ready to get read...to other process.?? (0 Replies)
Discussion started by: Harry443
0 Replies
10. UNIX for Beginners Questions & Answers
Hi all,
First of all, sorry for the pastebin link. The code tags aren't working for me.
#!/bin/bash # while-menu-dialog: a menu driven - Pastebin.com
This is a channel "changer" shell script i'm working on. It uses dialog to display the menus.
It... (3 Replies)
Discussion started by: ignatius
3 Replies
LEARN ABOUT ULTRIX
mkfifo
mkfifo(3) Library Functions Manual mkfifo(3)
Name
mkfifo - make a FIFO special file
Syntax
#include <sys/types.h>
#include <sys/stat.h>
int mkfifo(path, mode)
char *path;
mode_t mode;
Description
The function creates a new FIFO special file whose name is path. The file permission bits of the new FIFO are initialized from mode,
where the value of mode, is one (or more) of the file permission bits defined in <sys/stat.h>. The mode argument is modified by the
process's file creation mask (see
The FIFO's owner ID is set to the process's effective user ID. The FIFO's group ID is set to the process's effective group ID.
Return Values
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
Diagnostics
The function will fail and the FIFO will not be created if:
[EACCES] A component of the path prefix denies search permission.
[EEXIST] The named file exists.
[ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire pathname exceeded 1023 characters.
[ENOTDIR] A component of the path prefix is not a directory.
[ENOENT] A component of the path prefix does not exist or the path argument points to an empty string.
[EROFS] The named file resides on a read-only file system.
[EFAULT] Path points outside the process's allocated address space.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EIO] An I/O error occurred while making the directory entry.
[ENOSPC] The directory in which the entry for the new FIFO is being placed cannot be extended because there is no space left on the
file system.
[ENOSPC] There are no free inodes on the file system on which the node is being created.
[EDQUOT] The directory in which the entry for the new FIFO is being placed cannot be extended because the user's quota of disk blocks
on the file system containing the directory has been exhausted.
[EDQUOT] The user's quota of inodes on the file system on which the FIFO is being created has been exhausted.
[ESTALE] The file handle given in the argument is invalid. The file referred to by that file handle no longer exists or has been
revoked.
[ETIMEDOUT] A connect request or remote file operation failed because the connected party did not properly respond after a period of
time which is dependent on the communications protocol.
See Also
mknod(1), umask(1)
mkfifo(3)