Path: utzoo!utgpu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!nucsrl!igloo!ddsw1!zane
From: zane@ddsw1.MCS.COM (Sameer Parekh)
Newsgroups: alt.hackers
Subject: Re: Explanation needed.
Message-ID: <1991Mar09.041413.8570@ddsw1.MCS.COM>
Date: 9 Mar 91 04:14:13 GMT
References: <10133@sales.GBA.NYU.EDU> <1991Mar3.215703.15745@csusac.csus.edu> <1991Mar4.025618.29347@cs.cmu.edu>
Organization: ddsw1.MCS.COM Contributor, Wheeling, IL
Lines: 26
Approved: yes


	I sort of did a similar thing, with worse results. . .I wrote
a shell script to see who logged on and off. . .(Little did I know
that we had watch.)  I 'who' into a file, then 'who'ed into another
file, 'diff'ed them, and then copied the new file to the old file. . .
very simple, very dumb.  I ran the program it worked fine, I was
using a dial-up so I had no idea what was going on on the other end.
	So I hung up, but I forgot to kill the process. . .(On my
system I didn't have to do a nohup, neither I nor my sysadmin knows why.)
So then someone else called on the same tty and got the diff messages. . .
needless to say, he was confused. . .then I called and he 'talk'ed to me.
I explained what was going on and I killed the process.
	Then one day my sysadmin got mad at me. . .I had no idea why. . .
because I didn't put a sleep into the script it was executing really
quickly and taking up MUCH CPU time. . .(I had no idea, honestly.)
So I deleted it. . .
	Then a month or so later, this guy I spoke to earlier said
that he ran the program at work, and the drive went crazy. . .I suggest
you DO NOT TRY THIS AT HOME!!!!

	(I'm sure all of you knew this would happen, I am just relating
my story. . .my first, I am new to the world of UNIX.)


-- 
zane@ddsw1.MCS.COM