10-12-2005
Pipes and fifos cannot overflow. A fifo, aka named pipe, is more of a interprocess communication mechanism than a file. Unlimited writes to fifos are required by Posix. If you exceed PIPE_BUF, you lose the guarantee of atomicity. This only has an effect in the case of multiple writing processes. Some people wanted a PIPE_MAX and such a constant is available but it is the same as the max value in a ssize_t field. Setting O_NONBLOCK and writing more than PIPE_BUF will result in partial writes and a poorly designed application could lose data under those circumstances, but that is not exactly an overflow.
With one process reading from a pipe and another writing to a pipe, they will take turns running. In theory, a pipeline like:
yes | cat > /dev/null
can run for all eternity and that continues to be true if a fifo is used instead.
10 More Discussions You Might Find Interesting
1. HP-UX
I would like to know if the following can be done.
route output from an sql select directly to a pipe and compress it at the same time.
regards
Albert (2 Replies)
Discussion started by: booyena1
2 Replies
2. Programming
I currently stuck on a simple program that requires unix pipe. I'm have never programmed with unix pipe before, so if anyone can point me to the right different will be greatly appreciated!
I'm suppose to write a program that the parent spawns many child processes and each of the child process... (1 Reply)
Discussion started by: meh
1 Replies
3. Shell Programming and Scripting
Could one of you shad some light on this:
I need to split the file by determining the record count and than splitting it up into 4 files. Please note, this is not a fixed record length but rather a "|" delimited file.
I am not sure as how to handle reminder/offset for the 4th file.
For... (4 Replies)
Discussion started by: ddedic
4 Replies
4. UNIX for Dummies Questions & Answers
Looking for examples/definition of what the term Pipe means in UNIX. Please provide answers and illustrations if possible or direction. Thanks!:) (5 Replies)
Discussion started by: dfrost126
5 Replies
5. UNIX for Advanced & Expert Users
I am pretty new to UNIX. My client has a requirement where in a directory we have some files with somewhat similar name
like test_XX.txt, test_XY.txt, test_XZ.txt, test_ZZ.txt, test_ZY.txt, test_ZX.txt, test_YY.txt......Out of these files
few files have 0 bytes. Is there a way where we can go... (7 Replies)
Discussion started by: RubinPat
7 Replies
6. Shell Programming and Scripting
I am trying to convert a txt file that includes one long string of data. The lines are separated with hex value 7C (for pipe).
I am trying to process this file using SQR (Peoplesoft) so I thought the easiest thing to do would be to replace the eol char with a CRLF in unix so I can just... (4 Replies)
Discussion started by: sfedak
4 Replies
7. UNIX for Dummies Questions & Answers
EDIT: Nevermind, called a friend who is good at this stuff and he figured it out :D
Hi all,
So I'm trying to teach myself to write programs for unix in c. I am currently creating a program, and I need to pass a struct through a pipe, but I can't figure out how.
The struct I want to pass... (0 Replies)
Discussion started by: twnsfn34
0 Replies
8. Shell Programming and Scripting
Hi
I am new to Unix Shell scripting have a requirement where I have to replace the "unix 1 byte delimiter" with the "pipe" separator and also remove any carriage returns and line feeds if any
The Source File
4 QFH Jungle Hill 32-34 City Road London SE23 3UX
the output should be ... (3 Replies)
Discussion started by: dJHa
3 Replies
9. Shell Programming and Scripting
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... (2 Replies)
Discussion started by: naveen mani
2 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
I'm creating a program which reads millions of bytes from the PIPE and do some processing. As the data is more, the idea is to read the pipe parallely.
Sun Solaris 8
See the code below:
#!/bin/sh
MAXTHREAD=30
awk '{print $1}' metadata.csv > nvpipe &
while
do
... (3 Replies)
Discussion started by: mr_manii
3 Replies
LEARN ABOUT MOJAVE
sigtrap
sigtrap(3pm) Perl Programmers Reference Guide sigtrap(3pm)
NAME
sigtrap - Perl pragma to enable simple signal handling
SYNOPSIS
use sigtrap;
use sigtrap qw(stack-trace old-interface-signals); # equivalent
use sigtrap qw(BUS SEGV PIPE ABRT);
use sigtrap qw(die INT QUIT);
use sigtrap qw(die normal-signals);
use sigtrap qw(die untrapped normal-signals);
use sigtrap qw(die untrapped normal-signals
stack-trace any error-signals);
use sigtrap 'handler' => &my_handler, 'normal-signals';
use sigtrap qw(handler my_handler normal-signals
stack-trace error-signals);
DESCRIPTION
The sigtrap pragma is a simple interface to installing signal handlers. You can have it install one of two handlers supplied by sigtrap
itself (one which provides a Perl stack trace and one which simply "die()"s), or alternately you can supply your own handler for it to
install. It can be told only to install a handler for signals which are either untrapped or ignored. It has a couple of lists of signals
to trap, plus you can supply your own list of signals.
The arguments passed to the "use" statement which invokes sigtrap are processed in order. When a signal name or the name of one of
sigtrap's signal lists is encountered a handler is immediately installed, when an option is encountered it affects subsequently installed
handlers.
OPTIONS
SIGNAL HANDLERS
These options affect which handler will be used for subsequently installed signals.
stack-trace
The handler used for subsequently installed signals outputs a Perl stack trace to STDERR and then tries to dump core. This is the
default signal handler.
die The handler used for subsequently installed signals calls "die" (actually "croak") with a message indicating which signal was caught.
handler your-handler
your-handler will be used as the handler for subsequently installed signals. your-handler can be any value which is valid as an
assignment to an element of %SIG. See perlvar for examples of handler functions.
SIGNAL LISTS
sigtrap has a few built-in lists of signals to trap. They are:
normal-signals
These are the signals which a program might normally expect to encounter and which by default cause it to terminate. They are HUP,
INT, PIPE and TERM.
error-signals
These signals usually indicate a serious problem with the Perl interpreter or with your script. They are ABRT, BUS, EMT, FPE, ILL,
QUIT, SEGV, SYS and TRAP.
old-interface-signals
These are the signals which were trapped by default by the old sigtrap interface, they are ABRT, BUS, EMT, FPE, ILL, PIPE, QUIT, SEGV,
SYS, TERM, and TRAP. If no signals or signals lists are passed to sigtrap, this list is used.
For each of these three lists, the collection of signals set to be trapped is checked before trapping; if your architecture does not
implement a particular signal, it will not be trapped but rather silently ignored.
OTHER
untrapped
This token tells sigtrap to install handlers only for subsequently listed signals which aren't already trapped or ignored.
any This token tells sigtrap to install handlers for all subsequently listed signals. This is the default behavior.
signal
Any argument which looks like a signal name (that is, "/^[A-Z][A-Z0-9]*$/") indicates that sigtrap should install a handler for that
name.
number
Require that at least version number of sigtrap is being used.
EXAMPLES
Provide a stack trace for the old-interface-signals:
use sigtrap;
Ditto:
use sigtrap qw(stack-trace old-interface-signals);
Provide a stack trace on the 4 listed signals only:
use sigtrap qw(BUS SEGV PIPE ABRT);
Die on INT or QUIT:
use sigtrap qw(die INT QUIT);
Die on HUP, INT, PIPE or TERM:
use sigtrap qw(die normal-signals);
Die on HUP, INT, PIPE or TERM, except don't change the behavior for signals which are already trapped or ignored:
use sigtrap qw(die untrapped normal-signals);
Die on receipt one of an of the normal-signals which is currently untrapped, provide a stack trace on receipt of any of the error-signals:
use sigtrap qw(die untrapped normal-signals
stack-trace any error-signals);
Install my_handler() as the handler for the normal-signals:
use sigtrap 'handler', &my_handler, 'normal-signals';
Install my_handler() as the handler for the normal-signals, provide a Perl stack trace on receipt of one of the error-signals:
use sigtrap qw(handler my_handler normal-signals
stack-trace error-signals);
perl v5.18.2 2013-11-04 sigtrap(3pm)