Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!talcott!panda!genrad!decvax!ittatc!bunker!wtm
From: wtm@bunker.UUCP (Bill McGarry)
Newsgroups: net.unix-wizards
Subject: Re: Eliminating PID # from background jobs
Message-ID: <1093@bunker.UUCP>
Date: Fri, 21-Feb-86 10:48:06 EST
Article-I.D.: bunker.1093
Posted: Fri Feb 21 10:48:06 1986
Date-Received: Mon, 24-Feb-86 06:13:29 EST
Reply-To: wtm@bunker.UUCP (Bill McGarry)
Organization: Bunker Ramo, Trumbull Ct
Lines: 20


In article <1848> Marc Ries (ries@trwba) wants to run a background
job from his .profile.  He does NOT want the PID to be printed but
still wants the standard output of the background job to go to the
terminal.

Well, there may be other ways to do this but one way would be to
have a separate shell script call the background job.  For example,
call this shell script "run_back".  This script would just contain:

	myprog&

Then in your .profile, just run "run_back" (NOTE: Do NOT run this in
background).

Results?:  "run_back" returns immediately.  No PID # is printed, yet
"myprog" output will go to the terminal.

				Bill McGarry
				{decvax, ittatc, philabs}!bunker!wtm