Why doesn't this dup2 functionality work?

Consider this code:

Code:

---

#include <unistd.h>    //dup2, STDIN_FILENO, STDERR_FILENO

int main(void)
{
  dup2(STDIN_FILENO, STDOUT_FILENO);
  while(1);
  return 0;
}

---

Basically, I'm trying to redirect stdin into stdout.
The way I am trying to do this is directly - Any message coming in through the input socket fb goes directly into the stdout socket fb without buffering anything in memory in my program.
dup2 copies over socket so STDIN and STDOUT were the same. I was hoping this would allow for any signal coming from STDIN to go to STDOUT.

Unfortunately this does not work. Is there any way possible to get this to work?
This would be a good optimization over buffering it in between..
I know it may sound impossible due to some limitation in linux, but I want to see if there is something I don't know that may enable it.
Maybe blocking vs nonblocking mode? Or something else?

[Note: this is a unix programming question, not a C programming question].

It doesn't work because you're not using dup2() for its intended purpose.

dup2() is for duplicating file descriptors, not for piping data from one stream to another. Look up the pipe() function if you want to redirect the output from one program to the input of another (but not the reverse).

If you want data copied from stdin to stdout, then you need a loop that reads data from stdin (for example, by calling fgetc()) and writes it to stdout (for example, by calling fputc()).

Do you see anything wrong with this code?:

Code:

---

#include <unistd.h>    //dup2, STDIN_FILENO, STDOUT_FILENO


int main(void)
{
  int socketPipe[2]; //0 = read, 1 = write
  pipe(socketPipe);


  dup2(socketPipe[0], STDIN_FILENO);
  dup2(socketPipe[1], STDOUT_FILENO);


  while(1);
  return 0;
}

---

Quote:

---

Originally Posted by LiteHacker

Do you see anything wrong with this code?:

Code:

---

#include <unistd.h>    //dup2, STDIN_FILENO, STDOUT_FILENO


int main(void)
{
  int socketPipe[2]; //0 = read, 1 = write
  pipe(socketPipe);


  dup2(socketPipe[0], STDIN_FILENO);
  dup2(socketPipe[1], STDOUT_FILENO);


  while(1);
  return 0;
}

---

---

Order of operations seem wrong to me. Your seem to be piping garbage in to garbage out.

Tim S.

pipe doesn't make much sense outside the context of two processes talking to each other, a parent and child (who can inherit a set of pipes from the parent). Thus, you would need two processes (e.g. by using fork). You should read through some examples and tutorials to get a handle on those functions and how they're used. Here, Let me google that for you. This link in particular looks useful: c - Using dup2 for piping - Stack Overflow.

Also, as the SO article suggests, read the man pages for pipe and dup2. The pipe man page actually has a nice pipe example.

EDIT: I may have slightly misunderstood what you want. If you simply want stdin be echoed to stdout exactly as is, then no, I don't think what you want is possible with some pipe/dup2 trickery. I think the solution is much more complex than that. Is there a reason you're trying to optimize, or is this just premature optimization?