C language, in Linux. Using system calls, not print statements. Program should only use system calls for obtaining input and creating output

When using any system call (or library call), be sure to read the man pages to be sure you understand its behavior, in particular how to interpret return codes A few suggestions: Build your program in stages. Some ideas are below, but you might break each step down further. Check return codes from all system calls. It may be helpful to write small programs that experiment with system calls individually. Programs should be created by first writing an outline that can be used to create comments in your program. When using neww functions and constructs, confirm each block of code for each comment is working. During development, this might be done using a debugger or by adding print statements. 1. piper Write a program that creates a two child processes. The parent should communicate with the two children through pipes. The parent should read numbers from STDIN and send them to both children. The numbers are input as ASCIl values separated by spaces or newlines. One child should add the numbers and save the results in a file, addout and the other child should multiply the numbers and save the result to multout. Be sure that results are saved as ASCII strings The solution should be insensitive to the number of input characters (i.e. input from STDIN should terminate with a Control-D). Be sure that everyone "cleans-up" before terminating