why you don't use wait in parent process(else part) because both process are running parallel

Why is channel underrated, I love how you explain just so much.. stuff that took me weeks to grasp just in one video. I wish I found you earlier

As a CS student I’ve watched countless tutorials and you are by far one of (if not) the best instructors I’ve come across

dude, all tour videos from the playlist which includes this video have helped a lot in university. thank you so much and keep it up!

No word can describe how much your videos helped me take my C a step fourther. Thank youuu 🙏❤

you're a legend you should be proud

Wow, this is the most clear and concise coding lessons I have found on youtube. Perfect pace, audio and video quality is great, everything clear. Thank you so much. I was thinking of dropping my university OS course but now I think I may be able to pass with your videos.

Thank you so much for making and posting the Unix Processes in C series of videos, it helps me a lot !!!

Your videos are excellent. Really helpful to all IT students out there. Short and straight to the point. And since they explain the basics of every subject so well the rest of the studying is easily done. Keep up the good work.

I've been watching your videos, like how you take the time to explain things which might not always be so obvious. You are the only one who has (good) tutorials on IPC, coulnd't find any other, thought I was lucky when I saw you made two videos on IPC but then checked your channel and saw you've not only covered looots of IPC but also have a huge library of videos on C. So surprising due to how little views/subs you have, very underrated. I must ask, I tried to setup the IDE you use, visual studio code and couldn't get it to run a program, tried looking up how to do it but couldn't find anything clear on it for ubuntu, seems rather advanced to set it up so everything works smoothly? Spent the whole day looking for a good IDE, tried Clion, which froze upon loading project and geany which was no better than texteditor imo :/

Thank you so much for recording this video! I have an OS class at school and the professor never taught us anything about this. Then he just released a project and I was hopeless until found this video!

This video just saved me 2 hours of reading explaining what should be a simple concept. Thank you so much =D

This is amazing! What my professors never taught, it is explained here so succinctly. Thank you for making this video!

You are amazing and an amazing teacher, the way you explain is so clear and concise. 15 min of your videos is about a month or two of school classes. You deserve AT LEAST 150k subs

It was really helpful, thank you. A complex concept can only be simplified in this way.

youtube's best c narrator 👑👑

I haven't understood forks and pipes all semester, but these two videos that you have were very well explained! Thank you so much, I might just pass my exam lol

Thank you so much, i wish my professors explained this well

You're an amazing teacher... and cute ha! Thanks for the tutorials!!!!

You literally saved my lab grade! Thank you so much for this very clear tutorial!

Thanks! I spend hours trying to figure out my problem before finding this video and fixed with a few minutes of starting

Not all heroes wear capes...Some make useful tutorial tooo ... thanx buddy!!!

Awesome videos no doubt. This playlist is the lifeline of my OS labs this semester. I have one suggestion for you; it would be better if you use an online board and some diagrams when explaining codes. Though I understood most of the explanations, I recommended this playlist to one of my friends and he didn't understand many things. not everyone has good imagination skills. Subscribed your channel. God bless you.

You have clear concepts with nice articulating skills. Thankyou :)

00:00 - Introduction to inter-process communication and the purpose of the video. 01:20 - Explanation of pipes as a method of inter-process communication. 02:40 - Basic syntax and functions for creating pipes in C. 04:15 - Demonstration of creating a pipe in C with a simple example. 06:00 - Discussion of reading from and writing to pipes. 07:30 - Example of parent-child process communication using pipes. 10:00 - Handling errors and closing pipes. 12:00 - Summary and conclusion.

this seem to me impossible while studying in uni,but now u have explained it really good

You're doing God's work 🙏🙏 💯

Hey! I like your videos! The only thing I suppose was wrong in that one is that your doesn't close the descriptor in case of write or read error and return straight away

You are legend man.

You're explaining that very clearly. Thank you, it helped me very much!

thanks for the video. you saved me. I love you. hope you have a good life :')

THis is one of the best video that I had liked Thanks you very much

Man, you are my savior!

You sound just like Shaggy lol Thank you for the lesson!

Thank you very much sir , you have a very good explication , thanks a lot from Algeria ❤️

Thanks a ton for this video, This cleared up so many things to me

Good Explanation... Really helps to solve the college assignments solution.

Thank you for this tutorial, it helped me understand linux pipe :)

Your videos are a massive help!

thanks for your video! What should I do if I want to get some complex return value like array of class object from child process ?

great teaching skills, thank you. Understandable after watching for the first time.))

Very nice explanation! Thank you very much for your content!

Absolutely love this content, thank you!!

oh thank god you have a video on this

great lesson hairline man

You are awesome, I really understood the topic with your explanations. Thanks you so much....

thank you this was really helpful and it saved me a lot of time

These vids are damn helpful for my OS practical classes.Is there a video where you show how you set up vs code and the debugger for C?I use sublime text now but without debugger.Thanks

you are amazing. thank you for making this video!

Love your videos, thank you!!

Hello and thx for the video. One thing that confused me a little bit is why do we close fd before making some operation. It seems to be more logical if pipe would read from fd0 and then write to fd1. But looks like it’s two different processes.

Thank you for sharing your knowledge, that was very helpful

Super clear video! Do you have any extension for VS to show a little explanation of the functions when you have your cursor above?, when I do so it only shows me the prototype of the function

Clear information. Great! This things are hard to Find on this kind of topics. Thank you and here is your like and subscribe from Argentina

Great video, understand pipes now. Cheers!

quality content! What book would you recommend reading about operating system?

I came here for 6:54. I was wondering why in my professor's sample code you have to close the other end of the pipe. Turns out it's very simple -- it's because we inherit it but we're not using it haha

fantastic video

you are the best

hey, how can you see the documentation for the function, i have VS code and C/C++ extension ,but i dont have the mehod documentations

Very well explained! Thank you!

This video was quite helpful!

@CodeVault , why cant we use a global valiable in that program declared before fork() and just store the input value in that variable?

Thanks a lot for the wonderful video, I have a question, why do we need to communicate between processes?

Excellent tutorial. Thanks a lot.

Explanation is good but there is correction here. Else part is parent part of process because fork return number is non zero for Parent process only.

Really helpfull explanation and example. Many thanks dude :D

Thank you soo much man.

I have multiple question. Why u dont wait at the end of the parent? Since u dont wait, why did the child process always run before the parent? For exemple why u didnt get an error telling u that value y isnt initialised cause we learned that u never know which process execute first if u dont wait. Second, how did u open the fd? Dont u need to use open() after using a pipe? Cause pipe juste gives u fd, but they dont actually open them right? + dont u need to give them the permission to either read or write in them? And last question, since u use a protection for ur fork, ur write and ur read, why didnt u close the fd before returning each error value? Cause what i see here is that if u fail to write, then u return 2 if i remember correctly, and only fd[0] is closed, while fd[1] remains open no? Except from these questions, i find ur videos really helpful thanks 🙏 , cause i noticed that since the beginning i only ask questions without thanking u lol 😂, sry about that.

Hi, what is your VSCode extension which shows you the function's description ? Thank you !

Thanks for the explanation. QUESTION : if there is an error when you either read or write and return the program, Will the file descriptors be left open?

Please share your keyboard model, it sounds delicious!

Okay in 8:40 , let's suppose you have corrected the code there as said by someone from the comments by adding wait(NULL) in the else block to make the parent wait for the child and executed it. One thing confuses me : how could you read from fd[0] in line 27 when you have closed that buffer in line 18? I am not used to use the function close. Any explanation for my confusion?

thank's!! It was really clear🙏

I have a question sir. Why we have to fork right after the pipe? Can't we just pipe first after fork? What is the difference? Apart from sir, everyone who knows the exact answer shall comment under my question too, i really welcome your thoughts. Thank you in advance

@CodeVault has real value

excellent, thank you very much for you work

ive been running the code using on VS code using a mac but the child process has been executing first, printing "Got from child process ..... then Input a number

Amazing, thank you so much!

what program do you use to run the code? we programmed c in codeblocks, but that obviously can't run these types of codes and i tried putty, but it's just problematic. also thank you so much for these videos, you're the reason i haven't failed yet in my operation system class.

Well explained... Simply amazing 🤩

thank you so much! very clear explications!

Make video on how to make Excel as dde server so that every second data in Excel may be poke out to trading platform or charting software

Thank you so much for this video! I'm only a bit confused because while following along with the code around 11 min in the video my output showed only 2 printf messages or just one when we removed the break. ➜ ./a.out wrote 8 result is 8 Why is that happening? does that mean that even with the break the parent process is too quick for the child even to give any form of output?

Dose this have to written in main?

Simple explanation! Thanks again

I may have missed the answer to this while I was skimming through the chat, but I'm curious to know why when I enter a string instead of a number as input for the child, a number is still returned?? Is this number a process id?? If so is it a process Id of the child or the parent??

Awesome thanks a lot! Please need some guidance on how to get the output of printf of another program (child) then receive that in the main program (parent) but not after the child is closed or done?

i have been watching you videos and there are very good . but im trying to use system(); to call nmap and mysql togther and feed one with inforamtion with the other .do you have any videos on piping console output and input

Hello, Thanks for these usefull videos! I was wondering how you can see on VS the definitions of functions that you call, for instance pipe : "Create a one-way communication channel [...] " Thanks for the help :) best

Why no wait() in the parent though? Does the parent wait by default till the user inputs something in scanf? Why does it work? That is confusing..

In this case, the parent process would try to read first, before the child process writes. Surprisingly, the code still works without wait() in the first line of else block. How does this work?

Excellent video.

Hi , Do you have to wait i the else part at the begenning of paper before reading from the pipe(fd[0]) for the child to write to fd[1] and finish its execution basically i was asking if you can a write call before anything is written to the pipe. please advices

what would happen if the user inputs -1? in this case wouldnt the if-statement return an error? if yes how could I deal with this unwanted behavior?

do you have some videos about mmap() function?. Thanks for this video.

thank you very much :)

Just a question , shouldn't you put an exit a then end of your child? Because if you make a wait(null) in your father process it might be stuck forever if the child never dies?

Help me with this exercise please I don't understand how to do it 2) Write a program that receives a variable number of filenames from the command line. commands. For each file name the program must create a child process that: - Print your PGID, PPID, PID and file name; Y - Use one of the exec() family functions to execute: wc -l file_name. Considerations: - Child processes must be executed concurrently. - The parent process must indicate which child process is ending and indicating what way ends (Normal or by a signal). - If no filename is passed an error message should be displayed. - The system() system call cannot be used.

First of all thanks for the video, but I don't understand what happens when we return a number to exit a thread (ex: return 1 when an error occurs in opening the pipe). Does this number have a meaning or its printed on console window to indicate the part of the error or something like that?