Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!gatech!purdue!haven!wam!charlie
From: charlie@wam.umd.edu (Charles William Fletcher)
Newsgroups: comp.sys.next
Subject: Logout and printing
Keywords: Printing,logout,clobber
Message-ID: <1991Jan2.190441.7225@wam.umd.edu>
Date: 2 Jan 91 19:04:41 GMT
Sender: usenet@wam.umd.edu (USENET Posting)
Reply-To: charlie@wam.umd.edu (Charles William Fletcher)
Organization: University of Maryland at College Park
Lines: 22


Hopefully someone can explain and fix this for me--

I have a stand alone cube. I was printing several text files from Edit.
With still one file left to be printed I exited Edit and logout.
Since I have spent too much time on a network with a server I didn't
expect anything to happen-my mistake. I soon as I logged out the Hard
disk went crazy (looking for the now missng file????) I logged on and 
things returned to normal-but when I tried to print something I found
that the getty (or daemon or whatever) for the printer ahd been killed.
I decided to fix it later and logged off. Once again the hard drive
went crazy like it was looking for something. I logged in (to settle
down the HD) and powered off. This (of course) fixed my problems
when I rebooted.

Question: What happened? How do I prevent this in the future (short
of the obvious-ie, is there a parameter to be set?) Does this happen
under 2.0 where printing is done as a background process?

Thanks for the help,

Charlie