Reading from blocking fifo pipe in shell script Post: 302116677

10 More Discussions You Might Find Interesting

1. Programming

Pipe & fifo....

Could someone Help me with this code please? #include <stdio.h> #include <unistd.h> #include <sys/types.h> #include <sys/stat.h> #include <string.h> #include <fcntl.h> #define SIZE_B 256 /*buffer's size */ #define NUM_ARG 20 /* max number of args for any command */ int...

2. UNIX for Advanced & Expert Users

PIPE and FIFO buffer size

Hello! How I can increase (or decrease) the predefined pipe buffer size? Thanks!

3. UNIX for Dummies Questions & Answers

fifo or named pipe working?

Can someone explain to me the working of fifo() system call using simple C programs so that I can implement them in the UNIX environement?

4. Shell Programming and Scripting

Non-blocking pipe

Hello, Would this be an acceptable way of creating a non-blocking pipe. Basically I want to create kind of a server client arch. This code would be in the server, and I don't want to have to wait for clients to read before moving on to the next client. One problem I can see is if...

5. UNIX for Advanced & Expert Users

Why not SIGPIPE for readers of pipe/FIFO?

Hi This is a exercise question from Unix network programming vol2. Why the SIGPIPE signal is generated only for writers when readers disappear. why not it is generated for readers when writer disappears. I guess, if the writer didn't get any response like the reader gets EOF, it will...

6. Homework & Coursework Questions

FIFO possible blocking or unknown error

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Create a chat program using two FIFOs one for writing and the other for reading. The problem is something...

7. Programming

Pipe & fifo size limit

Hi guys. 1. how much is the size of pipe?(i mean the buffer size) 2. is this size different in various UNIX derivations? 3. what happens if we write to a full pipe? does it block until get some free space(the other side receive data) or returns an error? 3. FIFO s are physical files on the...

8. Shell Programming and Scripting

awk reading from named pipe (fifo)

I'm trying to read a fifo using awk and comming across some problems. I'm writing to the fifo from multiple processes invoked by GNU Parallel: mkfifo my_fifo awk '{ a = a + $2 } END { for (i in a) print i, a }' my_fifo | sort -nk1 > sorted_output grep -v '^@' massive_file | parallel...

9. Shell Programming and Scripting

Using Named pipe in shell script

Hi, I want to use a Named pipe to get input from a growing file for further processing. When I prototype this scenario using a while loop, the data is not written to the named pipe. This the script I use to get data into the Named pipe: #!/bin/ksh mkfifo pipe while (( n <= 10 )) do echo...

10. Shell Programming and Scripting

UNIX fifo concurrent read from a named pipe

I have created a fifo named pipe in solaris, which writes the content of a file, line by line, into pipe as below: $ mkfifo namepipe $ cat books.txt "how to write unix code" "how to write oracle code" $ cat books.txt >> namepipe & I have a readpipe.sh script which reads the named...

LEARN ABOUT OPENDARWIN

pipe

PIPE(2) 						      BSD System Calls Manual							   PIPE(2)

NAME

     pipe -- create descriptor pair for interprocess communication

SYNOPSIS

     #include <unistd.h>

     int
     pipe(int *fildes);

DESCRIPTION

     The pipe() function creates a pipe, which is an object allowing unidirectional data flow, and allocates a pair of file descriptors.  The
     first descriptor connects to the read end of the pipe, and the second connects to the write end, so that data written to fildes[1] appears on
     (i.e., can be read from) fildes[0].  This allows the output of one program to be sent to another program: the source's standard output is set
     up to be the write end of the pipe, and the sink's standard input is set up to be the read end of the pipe.  The pipe itself persists until
     all its associated descriptors are closed.

     A pipe whose read or write end has been closed is considered widowed.  Writing on such a pipe causes the writing process to receive a SIGPIPE
     signal.  Widowing a pipe is the only way to deliver end-of-file to a reader: after the reader consumes any buffered data, reading a widowed
     pipe returns a zero count.

RETURN VALUES

     On successful creation of the pipe, zero is returned. Otherwise, a value of -1 is returned and the variable errno set to indicate the error.

ERRORS

     The pipe() call will fail if:

     [EMFILE]		Too many descriptors are active.

     [ENFILE]		The system file table is full.

     [EFAULT]		The fildes buffer is in an invalid area of the process's address space.

SEE ALSO

     sh(1), read(2), write(2), fork(2), socketpair(2)

HISTORY

     A pipe() function call appeared in Version 6 AT&T UNIX.

4th Berkeley Distribution					   June 4, 1993 					 4th Berkeley Distribution

10 More Discussions You Might Find Interesting

1. Programming

Pipe & fifo....

Discussion started by: M3xican

2. UNIX for Advanced & Expert Users

PIPE and FIFO buffer size

Discussion started by: Jus

3. UNIX for Dummies Questions & Answers

fifo or named pipe working?

Discussion started by: lvkchaitanya

4. Shell Programming and Scripting

Non-blocking pipe

Discussion started by: cdlaforc