This may be the last video I watch of yours at least for a while as my semester is ending and I most likely will never write in C again. I thank you for helping me through my semester. You were a comforting and friendly face through the whole thing. You helped me on a lot of my assignments. You helped me understand programming much better as a whole. I will always be thankful.
I honestly can't believe this channel is so small because these videos are super informative and have been floating me through my systems basic class. Thank you for the great explanations!
thank you so much for this serie of videos! are very important for me and i used to study for my university! I am from argentina and i'm continue learning more trough your explanaitions (flawless, indeed)!!!
The handles that you get for pipes should already work with any Linux function that uses this type of handle. As for the C standard functions, I will make a video on it
I am more a c++ user but i really enjoy your videos and learn a lot from them! I have question: In c++ there is a function called freopen("filename", "w/r/a" stdin/stdout); Could that replace the whole dup2() thing in c; Is this a function works like dup2();
This is interesting. Indeed that freopen function is equivalent to open + dup2. The interesting part is this can be found in stdio.h, so it's actually in the C standard not just the C++ standard. An important difference is that freopen works with streams (FILE* types) whereas dup2 works with file descriptors (int types) and is specific to UNIX.
@@CodeVault I think he means saving the output of the ping command to a char array instead of creating a new file. If it is, I have the same doubt. For example I want to save the output of the command executed through execlp to a char array so I can then use the function strtok to get the different elements of the char array. Is it possible or do I have to save always to a file?
Great video, thanks! What if I want to redirect the standard output of a child process right into the parent process instead of redirecting it to a file? Can I use dup2() function with a pipe descriptor for that?
Nice work !! i love all the videos you posted I have one question from this video. If we overwriting STDOUT descriptor to custom file descriptor, i know some how it got reverted back (parent process printing in console). Could you explain why?
@@CodeVault no like we tried printf in child process after dup2 performed then the printed data present in custom file, the after child returns parent process block executes printf that time data i s printed in STDOUT itself right ?
Oh, wait. dup2 only changes the STDOUT file descriptor for the current process. If you've done that only for the child process, it won't affect the parent process at all.
In this case what we do in each process is then same, namely, increment the number by 1, so the order the process excecutes doesn't matter. But what if we do different things in process? For example, we want to multiply the number by 2, then add 2, then divide by 4, the order we do this definitely matters to the result, so how do we make sure the processes are excecuted in order? Thank in advance.
You can using pipes or using cross-process semaphores. This video: code-vault.net/lesson/sordz1xc2w:1603732432133 and its continuation code-vault.net/lesson/v5cml4fg0w:1610639843712 has a lot of the answers you are looking for
Does closing stdout cause problems if the output of my program is being piped to a second program. Will it cause a broken pipe and can I avoid it by first duplicating stdout then restoring afterwards?
I'm not to keen on using the Win32 API as it's all over the place. But if you dig deep enough you should be able to find something like what is on Unix systems.
@@CodeVault in windows there is a CreateProcess function which has ~10 arguments and the same is with other functions. That's why I learned python, it makes things easier
@@CodeVault in os module, you have os.system function which can execute a cmd command or any program. And also there is an subprocess module with "call", a very similar function to os.system. And I think there are more in the latter module I mentioned, but I know just what I used. os.system is ~like "execlp", if I said it's name right.
You need to use dup() in that case to store the old value. Here's a more in-depth answer: stackoverflow.com/questions/9084099/re-opening-stdout-and-stdin-file-descriptors-after-closing-them
The OS usually cleans up opened files descriptors after terminating the process but it's a good practice to close unused file descriptors (especially if it's a long-running process)
@@CodeVault when the standard output is closed first, then the file descriptor after open( ) will be assigned to the smallest integer of file descriptor table( that would be 1). i have tried this by myself. the output of the command is written in the .txt file, but the output of printf( ) was not written in either the file or the console.
Now your output appears in the VS Code terminal emulator. But at first it appeared in the actual Ubuntu command prompt. How did you make it appear in the Ubuntu command prompt?
In the beginning of the course I was using a virtual machine with Ubuntu but I switched to code-server instead due to technical difficulties. There's a setting "externalConsole" in your launch.json that you have to set to true. But it has to be on a Ubuntu machine of course.
Here's a good explanation on the topic: stackoverflow.com/questions/9084099/re-opening-stdout-and-stdin-file-descriptors-after-closing-them dup() is called to get a copy of the fd and then, they close the stdin/stdout. Right after that, by calling open(), they get the fd with id 0/1 since open uses the first available fd id
это интересно. Единственное я не понимаю как работает файловый дескриптор. Я понимаю что два процесса НЕ могут иметь один и тот же файловый дескриптор с номером 3. Но как эта 3 хранит и передаёт открытый файл ? Это очень сложный вопрос, и если переводчик позволит тебе понять суть вопроса и ты ответишь, будет замечательно.
The file descriptor is just an identifier. Every function that uses that file descriptor does some translation to find where exactly is the file amongst other details. This file descriptor concept is basically there so you won't have to manually store everything the read/write functions need to function, just a simple integer.
All the source codes for all the videos are available on the website: code-vault.net For this particular video, here is the link: code-vault.net/lesson/43zvcsz6o1:1603732432539
Basically you have to use dup(1) to get the handler for the stdout before replacing it. Here's an explanation: stackoverflow.com/questions/11042218/c-restore-stdout-to-terminal
It's just the permission code for having every type of user read/write/execute that file. (Albeit it's excessive in this case). Here's some documentation that should help out: www.linux.com/training-tutorials/understanding-linux-file-permissions/
Very good video and exactly what I was looking for but still this C++ code doesn't work (date still shows up on screen instead of in file) : int shell(bool showPrompt) { pid_t child1 = fork(); if (child1 == 0) { string naam = "eric.txt"; const char *bestandnaam = naam.c_str(); int bestand = open (bestandnaam, O_CREAT | O_WRONLY, 0777); if (bestand == -1) cout
This may be the last video I watch of yours at least for a while as my semester is ending and I most likely will never write in C again. I thank you for helping me through my semester. You were a comforting and friendly face through the whole thing. You helped me on a lot of my assignments. You helped me understand programming much better as a whole. I will always be thankful.
I honestly can't believe this channel is so small because these videos are super informative and have been floating me through my systems basic class. Thank you for the great explanations!
Not all heroes wear capes. Thank you very much for these lessons
You channel is 100% underrated, neatly organized and perfectly explained!
I appreciate your explanation and energy, all my peers watch your videos and helps us finish our projects , thank you so much.
Rewatched pausing video sometimes, making notes. At last got it. Thank you. Great explanation. You have a talent for explanation. Great job!
These are wonderful presentations. They're relevant, accurate, clear, succinct, and nicely done. Thank you.
Thank you so much for such a great video. Keep it up and I hope people will realize how fantastic this channel is.
Man you are absolutely amazing. You explain so simply what my professor and 2 TA's can't even give me basic intuition for.
THANK YOU
+1 Absolutely
I feel like you guy. I'm listening to this video and understanding in a language that i'm not that knowledge...Thanks a lot!!!
Thank you so much for releasing this video! It helped me a lots in OS classes!!!
Your content is just amazing, easy to understand.. really helpful, for sure deserve more viewers/subscriber,
Thanks again...really appreciate it..
This is a very good explanation!! Definitely saved me for my assignment
Your videos are legitimately amazing.
thank you so much for this serie of videos! are very important for me and i used to study for my university! I am from argentina and i'm continue learning more trough your explanaitions (flawless, indeed)!!!
this is awesome, so hard to find help on this online. Other sources either have no example or an example too complicated.
Helped me to undestand dup2. Love ur content, hope ur channel will grow bigger, u deserve it.
woow
you are amazing - thanks for the requested video!
great explanation!
Your videos are so informative better then my lecture in the class. it really helpful. Thank you for the this helpful content
Man, u are cool. Ty very much. My lecturer did not explain the material, but with your help, I learned everything on my own!!
Thank you so much for sharing your knowledge .
2021 first best thing is finding this channel.....
Great explanation, incredible. Thank you so much.
This is the most helpful video I have watched in my entire life. I am not even joking. Thank you so much!!
best teacher ever, I bingwatch you. Thank you very much for sharing!!!
smart teacher. great comprehension of the material and great explanation of the material
videos are super informative , wannted more video on pipes and dup2 on realtime application .
Thank you for the great explanations
I'm blown away by this video, thanks for showing these hidden tricks.
Great video!! This explanation will really help me on a project I'm working on
You are amazing! Thank you!
Perfectly explained, great work!
incredible video, thank you!!
life saver sir , thank you
thank you for this amazing video
Helped me a lot, thank you !
AMAZING. BEST CHANNEL EVER
omg)) dup2 is so doooope. i expected some trick with redirect, but this.. thanks a lot!
you are amazing.
YOU ARE THE MVP
this is an awesome video, thank you very much !!
Thanks for the video. It helped a lot
thank you so much you for your efforts...
you are the big boss ty
I love you man you just saved me
Thank you for the video
Good explanation thanks
it was helpful. Thanks a lot
thank you very much
very good explanation thank you
thank you mate
awesome video!
this is the best explanation
ty very much you're the best (again)
It was really helpful to understand the basic. Could you please explain How to redirect pipe in and out to standard functions ?
The handles that you get for pipes should already work with any Linux function that uses this type of handle. As for the C standard functions, I will make a video on it
YOU ARE A SAVIOR
Thank you!!!
Thanks a lot!
The best
Muy buenos videos, me han ayudado mucho 👍
I am more a c++ user but i really enjoy your videos and learn a lot from them! I have question: In c++ there is a function called freopen("filename", "w/r/a" stdin/stdout);
Could that replace the whole dup2() thing in c;
Is this a function works like dup2();
This is interesting. Indeed that freopen function is equivalent to open + dup2.
The interesting part is this can be found in stdio.h, so it's actually in the C standard not just the C++ standard.
An important difference is that freopen works with streams (FILE* types) whereas dup2 works with file descriptors (int types) and is specific to UNIX.
@@CodeVault ok thanaakss for answering my question!!!!
Very good
For all Windows guys its:
#include
and
_dup();
or
_dup2();
Great thanks
very nice
Very nice video
Good stuff broo...
Thank you very much for your great explanation! Just curious what IDE are you using?
Visual Studio Code. Here's a video on how you can also use it: code-vault.net/lesson/ublnbln8uf:1603733528013
That is such a nice explanation i love this guy
Really good..
You sure hear this alot , but you are really so good ! thx you !
Thanks
Hey, thanks for your awesome videos!
QUESTION: How do you go directly into a variable (e.g. char array) directly without opening a FILE?
I don't understand the question. What does it mean to "go directly into a variable"?
@@CodeVault I think he means saving the output of the ping command to a char array instead of creating a new file.
If it is, I have the same doubt. For example I want to save the output of the command executed through execlp to a char array so I can then use the function strtok to get the different elements of the char array. Is it possible or do I have to save always to a file?
Great video, thanks!
What if I want to redirect the standard output of a child process right into the parent process instead of redirecting it to a file? Can I use dup2() function with a pipe descriptor for that?
Yeah, in basically the same way, you'll have to dup2 the standard input of the parent process to that pipe as well
I want to create a c/c++ program to run MULTIPLE (say 10) c/c++ programs please help 🙏
Nice
Nice work !! i love all the videos you posted
I have one question from this video. If we overwriting STDOUT descriptor to custom file descriptor, i know some how it got reverted back (parent process printing in console). Could you explain why?
What got printed to the console? Maybe it was from the STDERR
@@CodeVault no like we tried printf in child process after dup2 performed then the printed data present in custom file, the after child returns parent process block executes printf that time data i s printed in STDOUT itself right ?
I'm asking how the control for file descriptor 1(STDOUT->customfile) return back to STDOUT in parent process
Oh, wait. dup2 only changes the STDOUT file descriptor for the current process. If you've done that only for the child process, it won't affect the parent process at all.
@@CodeVault But how do you revert it back if you ever need to do that?
In this case what we do in each process is then same, namely, increment the number by 1, so the order the process excecutes doesn't matter. But what if we do different things in process? For example, we want to multiply the number by 2, then add 2, then divide by 4, the order we do this definitely matters to the result, so how do we make sure the processes are excecuted in order? Thank in advance.
You can using pipes or using cross-process semaphores. This video:
code-vault.net/lesson/sordz1xc2w:1603732432133
and its continuation code-vault.net/lesson/v5cml4fg0w:1610639843712
has a lot of the answers you are looking for
i love u
Will it work trying to use pipe with dup2(fd[1] , 1) and dup2(fd[0] , STDOUT) ?
I want the pipe to write from stdin and read from stdout
Not really... You could write to a file the stdout of another and then read and redirect to a pipe
Thank you !
@@CodeVault
how can i reproduce behaviour of < {file name} in c? which descriptors i should redirect?
You could open the {file name} and just overwrite the stdin of the main process to be that file descriptor
So that means we can transfer date from an executable to another... now I can see more clear IPC.
Does closing stdout cause problems if the output of my program is being piped to a second program. Will it cause a broken pipe and can I avoid it by first duplicating stdout then restoring afterwards?
Yes, you could duplicate and restore the standard output
Helloo thanks for all of those video! But i whould like a course with more competitive programming with c and c++!!
Competitive programming? Can you give an examples of the types of videos you'd like to see?
I think in windows you can redirect the output of a program in cmd to null to surpress it, but not sure if the same is true in c/c++
I'm not to keen on using the Win32 API as it's all over the place. But if you dig deep enough you should be able to find something like what is on Unix systems.
@@CodeVault in windows there is a CreateProcess function which has ~10 arguments and the same is with other functions. That's why I learned python, it makes things easier
I'm not too familiar with python. How easy is it to create a process in Python?
@@CodeVault in os module, you have os.system function which can execute a cmd command or any program. And also there is an subprocess module with "call", a very similar function to os.system. And I think there are more in the latter module I mentioned, but I know just what I used.
os.system is ~like "execlp", if I said it's name right.
now before the termination of child process, if I want to print something to stdout in child process only, how do we do that ?
You need to use dup() in that case to store the old value. Here's a more in-depth answer: stackoverflow.com/questions/9084099/re-opening-stdout-and-stdin-file-descriptors-after-closing-them
@@CodeVault its clear now, thanks for the help brother !
I don't understand why you delete the "int file2 = " at the end, can you explain it more ? Great content btw !
Simply becuase the variable itself is not needed. We know file2 will always be STDOUT_FILENO in this situation so no need to store its value again
what if we dont close file after dup2(file, stdout_filenon); or it does not matter?
The OS usually cleans up opened files descriptors after terminating the process but it's a good practice to close unused file descriptors (especially if it's a long-running process)
@@CodeVault thanks for reply :P
what if we first close the standard output and then create the file. would it also work?
No, that wouldn't work
@@CodeVault when the standard output is closed first, then the file descriptor after open( ) will be assigned to the smallest integer of file descriptor table( that would be 1). i have tried this by myself. the output of the command is written in the .txt file, but the output of printf( ) was not written in either the file or the console.
Now your output appears in the VS Code terminal emulator. But at first it appeared in the actual Ubuntu command prompt. How did you make it appear in the Ubuntu command prompt?
In the beginning of the course I was using a virtual machine with Ubuntu but I switched to code-server instead due to technical difficulties. There's a setting "externalConsole" in your launch.json that you have to set to true. But it has to be on a Ubuntu machine of course.
How would you restore the fd of the stdout?
Here's a good explanation on the topic: stackoverflow.com/questions/9084099/re-opening-stdout-and-stdin-file-descriptors-after-closing-them
dup() is called to get a copy of the fd and then, they close the stdin/stdout. Right after that, by calling open(), they get the fd with id 0/1 since open uses the first available fd id
@@CodeVault thank you
это интересно. Единственное я не понимаю как работает файловый дескриптор. Я понимаю что два процесса НЕ могут иметь один и тот же файловый дескриптор с номером 3. Но как эта 3 хранит и передаёт открытый файл ? Это очень сложный вопрос, и если переводчик позволит тебе понять суть вопроса и ты ответишь, будет замечательно.
The file descriptor is just an identifier. Every function that uses that file descriptor does some translation to find where exactly is the file amongst other details. This file descriptor concept is basically there so you won't have to manually store everything the read/write functions need to function, just a simple integer.
Great video . Where can i get the code ?
All the source codes for all the videos are available on the website: code-vault.net
For this particular video, here is the link: code-vault.net/lesson/43zvcsz6o1:1603732432539
How can i restore STDOUT to File Descriptior 1
Basically you have to use dup(1) to get the handler for the stdout before replacing it. Here's an explanation: stackoverflow.com/questions/11042218/c-restore-stdout-to-terminal
Who else is here from CS 341 at UIUC 😂
why did he use 0777?
It's just the permission code for having every type of user read/write/execute that file. (Albeit it's excessive in this case). Here's some documentation that should help out: www.linux.com/training-tutorials/understanding-linux-file-permissions/
Very good video and exactly what I was looking for but still this C++ code doesn't work (date still shows up on screen instead of in file) :
int shell(bool showPrompt) {
pid_t child1 = fork();
if (child1 == 0) {
string naam = "eric.txt";
const char *bestandnaam = naam.c_str();
int bestand = open (bestandnaam, O_CREAT | O_WRONLY, 0777);
if (bestand == -1) cout
The code looks fine... Can you send me the executeCommand function?
@@CodeVault it just does a return execvp(date) and gives back an int as return code
@@CodeVault at least thanks to your video I know I'm on the right track. Maybe something more to do with the virtual machine I am using for execution.
Create more video!!!
Very soon, my friend :D