Scribd
Upload
2 views12 pages

Module-4 A. Process Control (USP) Notes

Module 4 USP notes

Uploaded by

premkumar74802
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
2 views12 pages

Module-4 A. Process Control (USP) Notes

Module 4 USP notes

Uploaded by

premkumar74802
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
PROCESS CONTROL — Mbp INTRODUCTION Process control is concerned about creation of new processes, program execution, and process termination. PROCESS IDENTIFIERS Dll getplatona, | Ronen pest IDofcaing poses pide getppiatvete Ae pr ere fling poe ets alr ong ult getetatvet; etwas five we Dofling os gid_t getgid(voia) ; | sc: al op D feta pose ees: ve pep Doing es fork FUNCTION An existing process can create a new one by calling the fork function. include pid_t fork (void) ; Returns: 0 in child, process ID of child in parent, 1 on error. The new process created by fork is called the child process. This function is called once but returns twice. The only difference in the returns is that the return value in the child is 0, whereas the return value in the parent is the process ID of the new child. a The reason the child's process ID is returned to the parent is that a process can have more than one child, and there is no function that allows a process to obtain the process IDs of its children, The reason fork returns 0 to the child is that a process can have only a single parent, and the child can always call getppid to obtain the process ID of its parent. (Process ID 0 is reserved for use by the kernel, so it's not possible for 0 to be the process ID of a child.) Both the child and the parent continue executing with the instruction that follows the call to fork. The child isa copy of the parent. For example, the child gets a copy of the parent’ ace, heap, and stack, Note that this is a copy for the child; the parent and the child do not share these portions of memory. Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNO9ISO16] RNSIT UNIX SYSTEM PROGRAMMING NOTES ———— + The parent and the child share the text segment. Example programs: Program 3 /* Program to demonstrate fork function Program name — forkl.c */ Hinclude Hincludecunistd,t> int main ) ‘ fork( ); Printe(*\a hello use"); hello usP helio usp Note : The statement hello USP is executed twice as both the child and parent have executed that instruction. Program 2 1/* Program name fork2.c */ ‘Hinclude ‘Hncludecunistd.t> Ant main( ) ci Print#("\n 6 sem"); fork(): printf(*\n hello USP"); ‘Note: The statement 6 sem is executed only once by the parent because itis called before fork and statement hello USP is executed twice by child and parent. [Also refer lab program [Link] File Sharing Consider a process that has three different files opened for standard input, standard output, and standard error. On return from fork, we have the arrangement shown in Figure 8.2. Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RN03ISO16] RNSI ___UNIX SYSTEM PROGRAMMING NOTES 38 table ent) file table wenode table file status fags wenode ‘current file offset information v-node pointer —} formation “current file size file status flags ‘current fle offset v-node Information vnode pointer vo information child process table en file status flags ‘current file offset Ais _ paler a0) fai v-node pointer —} v-node information Frode information ‘current filesize Figure 8.2 Sharing of open files between parent and child after fork Its important that the parent and the child share the same file offset. Consider a process that forks a child, then waits for the child to complete ‘Assume that both processes write to standard output as part of their normal processing. If the parent has its standard output redirected (by a shell, perhaps) it is essential that the parent's file offset be updated by the child when the child writes to standard output. In this case, the child can write to standard output while the parent is [Link] for it; on completion of the child, the parent can continue writing to standard output, knowing that its output will be appended to whatever the child wrote. IF the parent and the child did not share the same file offset, this type of interaction would be more difficult to accomplish and would require explicit actions by the parent. ere are two normal cases for handling the descriptors after a fork. Y The parent waits for the child to complete. In this case, the parent does not need to do anything with its descriptors. When the child terminates, any of the shared descriptors that the child read from or wrote to will have their file offsets updated accordingly. Both the parent and the child go their own ways. Here, after the fork, the parent closes the descriptors that it doesn't need, and the child does the same thing, This way, neither interferes with the other's open descriptors. This scenario is often the case with network servers, here are numerous other properties of the parent that are inherited by the child: © Real user ID, real group ID, effective user ID, effective group ID © Supplementary group IDs © Process group ID © Session 1D Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNOSISO16] NSIT UNIX SYSTEM PROGRAMMING NOTES Te Controlling terminal The set-user-1D and set-group-ID flags, Current working directory Root directory File mode creation mask ‘Signal mask and dispositions The close-on-exec flag for any open file descriptors Environment Attached shared memory segments Memory mappings Resource limits ecccccc0000 ‘The differences between the parent and child are > The return value from fork > The process IDs are different > The two processes have different parent process IDs: the parent process ID of the child is the parent; the parent process ID of the parent doesn't change The child's tms_utime, tms_stime, tms_cutime, and tms_cstime values are set to 0 File locks set by the parent are not inherited by the child Pending alarms are cleared for the child The set of pending signals for the child is set to the empty set The two main reasons for fork to fall are (a) if too many processes are already in the system, which usually means that something else is wrong, oF (b) ifthe total number of processes for this real user ID exceeds the system's limit. _AT When a process wants to duplicate itself so that the parent and child can each execute different sections of code at the same time. This is common for network servers, the parent waits for a service request from a client. When the request arives, the parent calls Cork and lets the child handle the request. The parent goes back to waiting for the next service request to arrive, _S- When a process wants to execute a different program. This is common for shells. n this case, the child does an exec right after it returns from the fork. vfork FUNCTION Y The function vfork has the same calling sequence and same return values as fork. V The vfork function is intended to create a new process when the purpose of the new process is to exec a ew program. Y The vfork function creates the new process, just like fork, without copying the address space of the parent into the child, as the child won't reference that address space; the child simply calls exec-{or exit) right after the vfork. ¥ Instead, while the child is running and until it calls either exec or exit, the child runs in the address space of the parent. This optimization provides an efficiency gain on some paged virtual-memory implementations of the UNIX System. Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNO3ISO16] UNIX SYSTEM PROGRAMMING NOTES Y Another difference between the two functions is that vfork guarantees that the child runs first, until the child calls exec or exit. When the child calls either of these functions, the parent resumes. Example of vfork function . Hnclude “apue. int glob = 6 /* external variable in initialized data */ Ant main(vold) int vai /* automatic variable on the stack */ pidt pid; printf ("before vfork\n"); /* we don't flush stdio */ Sf ((pid = véork(Q)) <0) ( err sys (*vfork error"); Te (pid == 0) ( Us chia */ globt+; (7* modify parent's variables */ (/* child terminates */ printe("pid = 4d, glob = 4d, var = d\n", getpid(), glob, var); exit (0) 7 ) Output $ -/[Link] before vfork pid = 29039, glob = 7, var = 89 exit FUNCTIONS Aprocess can terminate normally in five ways: Executing a return from the main function. Calling the exit function. Calling the exit or Exit function. imo UN ingens, (3) a fanctonin the standard Citra, whereas eta stem Executing a return from the start routine of the last thread in the process. When the last thread returns from its start routine, the process exits with a termination status of 0. Calling the pthread_exit function from the last thread in the process. The three forms of abnormal termination are as follows: Calling abort. This is a special case of the next item, as it generates the SIGABRT signal. Wihen the process receives certain signals. Examples of signals generated by the kernel include the process referencing a memory location not within its address space or trying to divide by 0. The last thread responds to a cancellation request. By default, cancellation occurs in a deferred manner: one thread requests that another be canceled, and sometime later, the target thread terminates. wait AND waitpid FU s ‘When a process terminates, either normally or abnormally, the kernel notifies the parent by sending the SIGCHLD signal to the parent. Because the termination of a child is an asynchronous event - it can happen at any time while the parent is running - this signal is the asynchronous notification from the kernel to the parent. The parent can choose to ignore this signal, or it can provide a function that is called when the signal occurs: a signal handler. | Aprocess that calls wait or waitpid can: | Preeses By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNOSISO16] RNSIT UNIX SYSTEM PROGRAMMING NOTES. ——————— eee eee ¥ Block, if all of its children are still running Return immesitely withthe termination status ofa child i child has terminated and fs wating fr its termination status tobe fetched ¥ Return immediately with an error, if it doesnt have any child processes Winclude Pid_t wait(int *statioc) ; pid_t waitpid(pid_t pid, int ‘etatloc, int options) ; Both return: process ID if OK, 0 (See later), or 1 on error. The differences between these two functions are as follows, The wait function can block the caller until a child process terminates, whereas wai tpid has an option that prevents it from blocking. » The waitpid function doesn't wait for the child that terminates frst; it has a number of options that control which process it waits for. {fa child has already terminated and is a zombie, wait returns immediately with that child's status. Otherwise, it blocks the caller until a child terminates. If the caller blocks and has multiple children, wait returns when one terminates, For both functions, the argument statloc is a pointer to an integer. If this argument is not a null pointer, the termination status of the terminated process is stored in the location pointed to by the argument. Print a description of the exit status Hinclude Void pr_exit(int status) { Af (WIFEXITED(status)) Print€("normal termination, exit status = 4d\n", WEXITSTATUS (status) ); Af (WIFSIGNALED (status) ) Print£ ("abnormal termination, signal number = ¢dts\n", WERMSIG (status) , #ifder WCOREDUMP WCOREDUMP(status) ?" (core file generated)" eu: Hels: fendi else if (WIFSTOPPED(status)) Print£ ("child stopped, signal number = ¢d\n", WSTOPSIG (status) ); ) Program to Demonstrate various exit statuses finclude “apue-h" Hinclude Int main (void) ‘ pid t pid; int status; if ((pid = fork()) < 0) err_sys ("fork error" else if (pid == 0) exit(7); 7? child */ if (wait(éstatus) != pid) /* wait for child */ err_sys("wait error") ; Pr_exit (status) ; /* and print its status */ Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNO91S016] Page 6 RNSIT UNIX SYSTEM PROGRAMMING NOTES ONS AE (phd = foxk()) < 0) (ere_aye ("fork error"); else if (pid = 0) entia +*/ abort () Generates SIGABRT */ Ae (wait(sstatus) != pid) wait for child */ orr_ays ("wait error"); pr_exit (status) ; and print ite status */ Af ((pid = fork ()) < 0) ‘err_sys ("fork error") ; else if (pid = 0) child */ ‘status /= 0; divide by 0 generates SIGFPE */ Ae (vait(cetatus) 1= pia) wait for child +/ rs(*wait error") ; and print its status */ The interpretation of the pid argument for wai tpid depends on its value: Waits for any child process. inthis respect, waitpid is equivalent to wait. ‘Waits for the child whose process 1D equals pid. Waits for any child whose process group ID equals that of the calling process. Waits for any child whose process grouplID equals the absolute value of pid. Koon ce nee Es Netery Description’ feasecsscrih} True if status was returned for a child that terminated normally. In this case, we can execute WexrTstArus (status) to fetch the low-order 8 bits of the argument that the child passed to exit, _exit,or_Bxit. peas aod eit} True if status was: teturned!for'a child that terminated abnormally, by receipt ofa signal that it didn't catch. In thiscase, we can execute WTERNSIG (status) to fetch the signal number that caused the termination, Additionally, some Implementations (but not the Single UNIX Specification) define the macro ‘cOREDUME (status) that returns true if a core file of the terminated process was generated. ; error e Tc) ‘True if status was returned for a child that is currently stopped. In this case, we can execute WSTOPSIG (status) to fetch the signal number that caused the child to stop. eos l eth) ‘True if statlis\wasireturnéd foria'child thathas been continuedattera job- controlstop) Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNOSISO16] ——$_—_——- UNIX SYSTEM PROGRAMMING NOTES ono If the implementation supports job control, the status of any child specified by pid that has been continued after being stopped, but whose status has not yet been reported, is returned. bcs The waitpid furiction Will HOt block if'a child specified by pid is not immediately available: in this case, the return Value is 0, 5 Liukuescidal Ifthe implementation supports job control, the status of any child specified by pid that has stopped, and whose status has not been reported since it has stopped, Is returned. The WIFSTOPPED macro determines whether the return value corresponds to a stopped child process. ‘The waitpid function provides three features that aren't provided by the wait function, Y The waitpid function lets us wait for one particular process, whereas the wait function returns the status of any terminated child. We'll return to this feature when we discuss the popen function. ¥ The waitpid function provides a nonblocking version of wait. There are times when we want to fetch a child's status, but we don't want to block. Y The waitpid function provides support for job control with the WuNTRACED and CONTINUED options. Program to Avoid zombie processes by calling fork twice include “apue.. Hinclude Int main (void) ( pidt pid; AE ((pid = fork) <0) ( = sys ("fork exror") ; de /* firet child */ AE ((pid = fork()) < 0) err_sys("fork error"); else if (pid > 0) ‘exit (0); /* parent from second fork == first child */ 7 + We'ze the second child; our parent becones init as soon * as our real parent calls exit() in the statement above. * Here's where we'd continue executing, knowing that when } * we're done, init will reap our status 7 sleep (2); Print ("second child, parent pid = #d\n", getppid()); exit (0); ) Af (waitpid(pid, NULL, 0) != pid) /* wait for first child */ ‘err_sys ("waitpid error"); I * We're the parent (the original process); we continue executing, * knowing that we're not the parent of the second child. / exit (0); ) ‘Output: § ./aout $ Second child, parent pid = 1 waitid FUNCTION The weitid function is similar to waitpid, but provides extra flexibility. Prepared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNO9ISO16] RNSIT UNIX SYSTEM PROGRAMMING NOTES Winclude Int waited (idtype_t idtype, id_t id, siginfo_t *infop, int options); Returns: 0 if OK, -1 on error ‘The idtype constants for waited are as follows: ‘Wait fora parti PLPGID — Wait for any child process in a particular process group: id contains the process group ID of the children to wait for. Wait for any chilé process: id Isianored. ‘The options argument isa bitwise OR of the flags as shown below: these flags indicate which state changes the caller 3 AND waits FUNCTIONS The only feature provided by these two functions that isn't provided by the wait, waitid, and waitpid functions is an additional argument that allows the kernel to return a summary of the resources used by the terminated process and all its child processes. ‘The prototypes of these functions are: include include Hinclude include pid_t wait (int *statloc, int options, struct rusage *rusage) ; pid_t waité (pid t pid, int *statloc, int options, struct rusage *rusage) ; Both return: process ID if OK,-1 on error ‘The resource information includes such statistics as the amount of user CPU time, the amount of system CPU time, number of page faults, number of signals recelved etc. the resource information is available only for terminated child process not for the process that were stopped due to job control, RACE CONDITIONS A race condition occurs when multiple processes are trying to do something with shared data and the final outcome depends on the order in which the processes run Leone eT? Prepared By: RAIKUMAR [Asst. Prof.] & DIVYA K [1RNO9ISO16} Page 9 RNSIT UNIX SYSTEM PROGRAMMING NOTES Example: The program below outputs two strings: one from the child and one from the parent. The program contains a race condition because the output depends on the order in which the processes are run by the kernel and for how long each process runs. ‘Hinclude “[Link] static void charatatine (char *); AE ((pid = fork()) <0) ( sys("fork exxor"); ) else ig (pid == 0) { charatatine ("output from child\n") ; ) else ( charatatime (“output from parent\n" ) exit (0); static void charatatine (char *str) ‘ char spte; inte setbuf (stdout, NULL) ; /* set unbuffered */ for (ptr = str; (c= *ptrtt) I= 0; } Putc(e, stdout) ; Qutput: 8 /[Link] output from child utput from parent out. {t from child ‘from parent out output from child output from parent rogram modification to avoid race condition Hinclude “apue.h* static void charatatine(char *); int main (void) * pidt pi a ‘TELL_WAIT() ; Lf (pid = fork()) <0) ( ezr_sys("fork error"); ) else Tf (pt yt WATT_PARENT() ; J+ parent goes first */ charatatine ("output from child\n") ; ) else ( charatatine ("output from parent\n"); TTELL_CHILD (pid) ; ) exit (0); , static void repared By: RAJKUMAR [Asst. Prof.] & DIVYA K [1RNO3ISO16] 0 RNSIT UNIX SYSTEM PROGRAMMING NOTES charatatine (char *str) A char pte; int er setbuf (stdout, NULL) ; /* set unbuffered */ for (ptr = str; (c= *ptr+t) '= 0; ) Pute(c, stdout) ; When we run this program, the output is as we expect; there is no intermixing of output from the two processes. exec FUNCTIONS When a process calls one of the exec functions, that process Is completely replaced by the new program, and the ‘new program starts executing at its main function. The process ID does not change across an exec, because a new process is not created; exec merely replaces the current process - its text, data, heap, and stack segments - with a brand new program from disk. There are 6 exec functions: Vinelude int execl(const char *pathname, const char *arg0,... /* (char *)0 */ ); int execv(const char *pathname, char *const argv [])? int execle(const char *pathname, const char *arg0,... /*(char *)0, char *const envp */ 7 int execve(const char “pathname, char *const argv{], char *const envp{]}s int execlp(const char *filename, const char *arg0, ... /* (char *)0 */ }7 int _execvp(const char *filenane, char *const argv (J}i All six return: -1 on error, no return on success. ‘The first difference in these functions is that the first four take a pathname argument, whereas the last two take a filename argument. When a filename argument is specified ‘* Iffilename contains a slash, itis taken as a pathname, * Otherwise, the executable file is searched for in the directories specified by the PATH environment variable. The next difference concerns the passing of the argument list (1 stands for list and v stands for vector), The functions exec, execlp, and execle require each of the command-line arguments to the new program to be specified as separate arguments. For the other three functions (execv, execvp, and execve), we have to build an array of pointers to the arguments, and the address of this array is the argument to these three functions. ‘The final difference is the passing of the environment list to the new program. The two functions whose names end in an e (execle and execve) allow us to pass a pointer to an array of pointers to the environment strings. The other four functions, however, use the environ variable in the calling process to copy the existing environment for the new program. iin exec [execlp SEsTeESEseeEHE abet STECH Roa TET erences snes eecec eee eee cesT eiecle x Ppa errr reer eer reer eee eee a ‘Meiterin name) P i The above table shows the differences among the 6 exec functi We've mentioned that the process ID does not change after an exec, but the new program inherits additional Properties from the calling process: © Process ID and parent process ID Prepared By: RAIKUMAR [Asst. Prof-] & DIVYA K [1RNOSISO16] RNSIT UNIX SYSTEM PROGRAMMING NOTES Real user ID and real group ID Supplementary group IDs Process group ID Session 1D Controlling terminal Time left until alarm clock Current working directory Root directory File mode creation mask File locks Process signal mask Pending signals Resource limits Values for tms_utime, tms_stime, tms_cutime, and tms_cstime. 9 0000000000000 execlp exec] execle build argo build arge build arge execvp try each, use [_execve PATH prefix caviron (system call) Relationship of the six exec functions Example of exec functions Yenv_init(] = { "USER=unknown", “PATH=/tmp", NULL }; int main (void) t Pidt pid; Af ((pid = fork()) <0) { ("fork error") ; (pid = 0) { /* specity pathnane, specify environment cle ("/hone/sar/bin/echoall", "echoall", “nyargi", "Mx ARG2", (char *)0, env_init) < 0) err_sys("execle error"); i Af (waitpid(pid, NOLL, 0) < 0) erz_sys(*wait error"); Af ((pid = fork()) <0) { err_sys ("fork error") ; } else if (pid == 0) ( /* specify filename, inherit environment +/ if (execlp("echoall", “echoall", "only i arg", (char *)0) < 0) erz_sys(“execlp error"); exit (0); : echoall nyargl MY ARG?

You might also like