09-18-2009
There's no arbitrary limit beyond whatever limit your system has for how many processes one user is allowed to create, how much memory one user is allowed to use, and how many pipes the kernel can keep around at once. You'd probably be allowed a few dozen at minimum before the system started refusing you, depending on what the processes actually are and what limits your sysop has set.
But that doesn't make it a good idea. Joining dozens of processes in a pipe-chain would be very inefficient since each one would need to take turns running and reading and writing. What is the goal here? There's probably a better way to do it.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I login to a specific machine (running Solaris 2.8; actually serveral machines behave this way), with a known good account, I don't get any shell prompt, and no screen responses to various commands such as ID and PWD. Any ideas on what is causing this, and how to change this behavior? (2 Replies)
Discussion started by: Mufasa
2 Replies
2. UNIX for Dummies Questions & Answers
Hi, I´m using SCO Unix 5.0.5 and I want to configure de variable PS1, so when I type the command:
cd /etc/
the prompt shows
/etc/_>
Is that possible with sh shell? I´ll appreciate your help.
Thanks, a Happy New Year! (1 Reply)
Discussion started by: diegoe
1 Replies
3. UNIX for Dummies Questions & Answers
currently, I set my prompt in my .cshrc file as:
set prompt = "%B%h %m %P %/ \n% "
I have to use certain shells for some specific tasks and would like to set different prompts depending on the type of shell that I am using. Any advice?
Thanks (3 Replies)
Discussion started by: dranNfly
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
I saw something in weird in Shell prompt.
I did the following steps
1) Typed ls -l and pressed ESC without entering
2) Typed "v" (please notice that I did not type "i" after "v"), which opened vi editor
3) I see the "ls -l" command that I typed in shell prompt
4) Without modifying... (6 Replies)
Discussion started by: bobbygsk
6 Replies
5. Shell Programming and Scripting
I'm new to working with pipes, so I don't know whether the following is expected behaviour or a bug on the part of an application.
Since Version 0.47, Inkscape provides a non-GUI interactive shell mode of operation. I am trying to time the program's performance in converting SVG files to PNG... (1 Reply)
Discussion started by: ccprog
1 Replies
6. Shell Programming and Scripting
Hi,
I want to change the shell prompt, using the cd command.
I have a shell prompt like this -
p78-mfx(dgaw1078/9781)$
Now i do this -
p78-mfx(dgaw1078/9781)$ cd log4j
here the shell prompt should change like this -
p78-mfx(dgaw1078/9781)log4j$ (6 Replies)
Discussion started by: arunkumarmc
6 Replies
7. AIX
Dear all experts,
I have a script written to compress a list of files, during compressing, some of the files are having same name. When the compressing started, the same name file will be prompted with message whether to overwrite the old file. I need to enter "y" to continue.
Is there any way I... (7 Replies)
Discussion started by: kwliew999
7 Replies
8. Shell Programming and Scripting
Hi,
I am learning shell scripting for the first time. I use AT&T Korn Shell, Version AJM 93u+ 2012-08-01, compiled from source on NetBSD.
So far I have managed to set up what I think is a useful and pleasing shell prompt, which can be seen in the image attached to this post.
The prompt is... (2 Replies)
Discussion started by: gezley
2 Replies
9. Homework & Coursework Questions
Good evening, I'm trying to do my own shell and I encountered some issues while creating it. Indeed when I try such a command I have
DAUPHINE> DAUPHINE> ls -l | grep terminal > fichier
DAUPHINE> cat fichier
My shell is named DAUPHINE
Whereas I should have:
Code:
... (0 Replies)
Discussion started by: AntoineCompagni
0 Replies
LEARN ABOUT DEBIAN
io_pipe
io_pipe(3) Library Functions Manual io_pipe(3)
NAME
io_pipe - create a Unix pipe
SYNTAX
#include <io.h>
int io_pipe(int64 pfd[2]);
DESCRIPTION
io_pipe creates a new UNIX ``pipe.'' The pipe can receive data and provide data; any bytes written to the pipe can then be read from the
pipe in the same order.
A pipe is typically stored in an 8192-byte memory buffer; the exact number depends on the UNIX kernel. Bytes are written to the end of the
buffer and read from the beginning of the buffer. Once a byte has been read, it is eliminated from the buffer, making space for another
byte to be written; readers cannot ``rewind'' a pipe to read old data. Once 8192 bytes have been written to the buffer, the pipe will not
be ready for further writing until some of the bytes have been read. Once all the bytes written have been read, the pipe will not be ready
for further reading until more bytes are written.
io_pipe sets d[0] to the number of a new descriptor reading from the pipe, and sets d[1] to the number of a new descriptor writing to the
pipe. It then returns 1 to indicate success. If something goes wrong, io_pipe returns 0, setting errno to indicate the error; in this case
it frees any memory that it allocated for the new pipe, and it leaves d alone.
SEE ALSO
io_readfile(3), io_createfile(3), io_socketpair(3)
io_pipe(3)