Please click on the Edit link under your post and add the [code] and [/code] tags (which I've already asked you to use).

To me that code is all wrong, here is how I create a blocking pipe:I just happen to make my pipes non-blocking, so following code I do use to make it non-blocking would be:I long ago wrote a blog entry on this subject, feel free to review, it is located here.

Dear Nevem Teve
1. I tried to use the pipe2 with this code:


ret_code = pipe2) fd, flags) ;
AT first flag was initialized to !O_NONBLOCK. After that I tried with flags =0.
I moved to this updated code:

int *pipe_fd

static int pipe_index = 0 ;
int ret_code ;
char pipe_index_char[10];

const std::string pipe_file_name_prefix = "PipeFile" ;

int pipe_flags ;
mode_t pipe_mode ;
std::string pipe_file_name ;

sprintf(pipe_index_char, "%u", pipe_index ) ;

pipe_file_name =
pipe_file_name_prefix+pipe_index_char ;
pipe_flags = O_RDWR | O_CREAT | O_TRUNC ; // O_WRONLY | O_CREAT | O_TRUNC ;
pipe_flags = pipe_flags & ~O_NONBLOCK ;
pipe_mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH ;

pipe_fd[0] = open( pipe_file_name.c_str() , pipe_flags, pipe_mode ) ;
if ( pipe_fd[0] == -1 )
{
std::cout << "Error in Creating Pipe for Read \n" ;
std::cout << "Errno is: " << strerror(errno) << "\n" ;
}

pipe_fd[1] = open( pipe_file_name.c_str() ,pipe_flags ,pipe_mode ) ;
if ( pipe_fd[1] == -1 )
{
std::cout << "Error in Creating Pipe for Write\n" ;
std::cout << "Errno is: " << strerror(errno) << "\n" ;
}
ret_code = fcntl (pipe_fd[0], F_SETFL, pipe_flags) ;
if (ret_code==-1 )
{
std::cout << "Error in setting the Block property. \n" << "Error Code = " << ret_code << "\n" ;
}

Best regards,
Yehuda

please read post#16

Where have you used the pipe2() function? It's not in that code. Why not read the recommendations to use [code] tags for one, and then secondly why not look at the 5 or 6 lines of sample code I posted and realize that this does exactly what you intend.

You are not using pipe() or pipe2() at all. Please review the man page. Why not give the blog entry a read too. There are code examples and there are additional blog entries to illustrate more complex things like how to use select() when you have multiple descriptors to check for inbound data.

I realize that persons like to do things their selves and thus feel they've learned better that way.

I myself learned these things by emulation, by searching for code examples, then doing experimentations much like you are, and then improving upon them.

But what I'm telling you is that while you are on the cusp of working with the concept of pipes, you are not actually correctly working with pipes in the classical Unix/Linux sense.

I believe my original experimentations were guided by the results of a web search where I used terms like "pipe programming example linux c" and I probably allowed the auto-complete to give me alternate suggestions.

The two main concepts to start with are (1) how to create a pipe at all, and then (2) how to use it. The next level of step is how to configure it. You say you want non-blocking I/O and I've told you that a natively created pipe is non-blocking I/O.

Once again, I'm not angry here, but what you're doing is making a case for the continual divisiveness between questioners and the offerers of answers. You'll get frustrated, because you've put in some effort, it's not correct, so you've been given some other recommendations, valid ones, and also not too complicated ones, and it appears that you're ignoring those things completely, as well as the points related to using [code] tags. We get frustrated seeing yet another questioner who ignores our suggestions, so we back off and figure, "Why bother? They're not reading what we write."