Path: utzoo!utgpu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!ucdavis!csusac!usenet
From: emmonsl@athena.ecs.csus.edu (L. Scott Emmons)
Newsgroups: alt.hackers
Subject: Re: Explanation needed.
Message-ID: <1991Mar3.215703.15745@csusac.csus.edu>
Date: 3 Mar 91 21:57:03 GMT
References: <10133@sales.GBA.NYU.EDU>
Sender: usenet@csusac.csus.edu (News account (alt))
Organization: California State University, Sacramento
Lines: 21
Approved: me@here

In article <10133@sales.GBA.NYU.EDU> elapinsk@sales.GBA.NYU.EDU ('Crazy' Emery Lapinski) writes:
>I once wrote a shell program that repeatedly did a 'ps -augx' but I suppose
>any command would work.  I then ran it with a 'nohup' and then hung up
>the phone, because it was going too fast and I couldn't get a chance to
>stop it.  I called back but as soon as I connected to the machine, this
>program was writing its output to my terminal even though I hadn't logged
>on yet.  I called back and went through telnet to another computer then
>telneted to my machine and could then kill it.  Can anyone explain how
>this might of happened and any other information along the same lines?

Yep...output from a program is attached to a tty, not to a user.  So, until
that program ended, output went to that tty; regardless of whether or not
anyone was logged onto it or not...As it turned out, completely by chance,
when you called back you were connected to the same tty that you were just
on! If someone else had connected to that tty right when you logged off, they
would have gotten your process' output...

			L. Scott Emmons
			---------------
	emmons@csus.csus.edu  <or>  ...[ucbvax]!ucdavis!csus!emmons
		Packet: kc6nfp@kg6xx.#nocal.ca.usa.na