ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From the little I read on bash's coproc, they just seem to be serving the same
purpose as pipes, that is, giving you a means to read form a program and write
to it, the only exception here is that the communication can be bidirectionnal,
whereas in a pipe the left part only writes to the right part, and the right
part only reads from the left part.
Is there any other thing I am missing from coprocs ? can they be defined as
bidirectional pipes ?
A coprocess is a shell command preceded by the coproc reserved word. A coprocess is executed asynchronously in a subshell, as if the command had been terminated with the ‘&’ control operator, with a two-way pipe established between the executing shell and the coprocess.
with other words:
Quote:
coproc command in Linux is a shell command which allows us to create a co-process that is connected to the invoking shell via two pipes.
And
Quote:
A pipe is a form of redirection (transfer of standard output to some other destination) that is used in Linux and other Unix-like operating systems to send the output of one command/program/process to another command/program/process for further processing. ... You can make it do so by using the pipe character '|'.
pipe is just a redirection operator, but shell needs to create a co-proc (or two) to make it work. So yes, they are similar to each other, but not the same.
In Linux/Unix, a "pipe" appears to be a file. You can read from it or write to it. What it actually is, though, is a unidirectional queue. A process that reads from it will be blocked until data arrives. A process that writes to it will be blocked if it has become full. It can be named or anonymous.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.