Properly Exiting LISP

In a past semester, the OIT administrator sent me the following
message:

  > Some of your students have left Lisp running in a loop.  Sometimes
  > several times on he same session server.
  > 
  > I suspect they may be using ctrl-Z thinking it kills Lisp and then
  > they logout.
  > 
  > I think that's what puts Lisp into a loop.
  > 
  > I'm just killing these when I find them.


It's important to make sure that you've terminated all LISP sessions
before you log out.  Sometimes you may think you've exited properly
but not done so.  To be sure, you can do this:

  % jobs

in response to which you might see

  [1]  + Suspended                     lisp
  [2]  + Suspended                     lisp

Each of those suspended jobs should be killed before you log out.  You
can do this by using the "kill" command with %n as its argument, where
n is the job number, e.g.

  % kill %1
  [1]    Terminated                    lisp

  % kill %2
  [2]    Terminated                    lisp

Alternatively, you can look for lisp processes by invoking

  % ps | grep lisp

which might give you something like this:

  2969 ttyp9    T        0:00.04 /usr/local/cmlisp/bin/lisp
 25787 ttyp9    S  +     0:00.00 grep lisp

This shows that there are two processes with "lisp" mentioned, but as
you can see only the first one needs to be killed.  You can give "kill"
the process ID rather than a job number:

  % kill 2969
  [1]    Terminated                    lisp

Be good citizens of the OIT cluster and make you've either exited or
killed all your LISP processes before logging off.