public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Raghuveer <rvk@gsecone.com>
To: "John T. Williams" <jtwilliams@vt.edu>
Cc: Silambu Chelvan <silambu_mdu@yahoo.com>, linux-newbie@vger.kernel.org
Subject: Re: Switching between foreground and background
Date: Tue, 23 Sep 2003 16:31:39 +0530	[thread overview]
Message-ID: <3F702813.8030200@gsecone.com> (raw)
In-Reply-To: <003501c3811f$610395a0$ed64a8c0@descartes>

John T. Williams wrote:

>I think part of the problem here might be conceptual.
>
>If I understand what you want, you'd like, on a signal, for your program to
>go into the background (still running but no longer blocking the terminal
>input/output). On another signal you would like the program to come back to
>the foreground.
>
>If this is the case, the problem you're facing is that the program being in
>the foreground and the background is actually part of the shell, not a
>property of the program running.  Most Shells provide a way to switch
>programs from the foreground to the background and back.
>BASH for example I could type
>
>$>./myprogram
>(cntr + Z) //suspends the current program and prings the prompt back
>$>bg  (runs the program in the background)
>
>The only way that I know of to force a program to run in the background in
>the code is to make it a daemon which is done by forking twice
>
>int main(  ) {
>   if(fork()==0)  {
>            if( fork() == 0 )  {
>                    program code starts here
>             }
>            exit(0);
>    }
>    exit(0);
>}
>  
>
I don't feel it's required to fork() twice for making it a daemon, once 
is enough. Ya, but should use setpgrp() or setpid() and close stdin, out 
and err after the fork and go to infinite loop.

-Raghu

>
>----- Original Message ----- 
>From: "Silambu Chelvan" <silambu_mdu@yahoo.com>
>To: <linux-newbie@vger.kernel.org>
>Sent: Monday, September 22, 2003 6:48 AM
>Subject: Switching between foreground and background
>
>
>  
>
>>Hi all,
>>
>>I have written some program with signal handler. Is
>>this possible, if
>>one of the signals registered with my program is
>>raised, my program
>>should goto background and should come to foreground
>>when some other of the
>>registered signal is raised. how to do it?
>>
>>Any function available to switch a process between
>>foreground and
>>background at runtime?
>>
>>with regards,
>>M. SilambuChelvan
>>
>>
>>__________________________________
>>Do you Yahoo!?
>>Yahoo! SiteBuilder - Free, easy-to-use web site design software
>>http://sitebuilder.yahoo.com
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.linux-learn.org/faqs
>>    
>>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.linux-learn.org/faqs
>
>  
>


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  parent reply	other threads:[~2003-09-23 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 10:48 Switching between foreground and background Silambu Chelvan
2003-09-22 15:37 ` John T. Williams
2003-09-22 15:51   ` Silambu Chelvan
2003-09-23 11:01   ` Raghuveer [this message]
2003-09-23 16:07     ` John T. Williams
2003-09-23 17:24       ` Mariano Moreyra
  -- strict thread matches above, loose matches on Subject: below --
2003-09-22 11:55 Markus Klotzbuecher
2003-09-22 12:38 ` Silambu Chelvan
2003-09-22 14:37   ` Markus Klotzbuecher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F702813.8030200@gsecone.com \
    --to=rvk@gsecone.com \
    --cc=jtwilliams@vt.edu \
    --cc=linux-newbie@vger.kernel.org \
    --cc=silambu_mdu@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox