On Sun, 21 Nov 2004 17:49:46 -0500, Bijoy Jacob Thomas <bijoyjth@xxxxxxxxx> wrote: > I dont think the kernel makes any distinction between foreground or > background processes. Its just something that it maintained by the > shell. When you run a program in the background by ./program &, you are > telling the shell to fork and exec the program but not to wait() on it > and return. Now, when you use the jobs command to see the background > processes, i believe the shell looks up its internal structures to find > out what processes it started in the background. jobs is a built-in > shell command. > > Oh yeah, the shell also detaches the background process from a terminal > ( so hitting a Ctrl-C will not send a signal to it). > > Regards, > Bijoy. > Thanks for your reply, But according to POSIX Terminal Interface, the terminal driver should send SIGTTIN and SIGTTOU to the process if an Background process tries to read or write the Terminal. How does Linux Kernel handle That? Thanks -- Manish Regmi -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
