Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!ucbvax!nrc.CA!Claude.P.Cantin
From: Claude.P.Cantin@nrc.CA
Newsgroups: comp.sys.sgi
Subject: getty errors.  For Kenny McDonald...
Message-ID: <9102141218.aa07213@VMB.BRL.MIL>
Date: 14 Feb 91 17:19:27 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34


I have tried to reply to Kenny McDonald (c60244@ccfiris.aedc) but
mail sent to him keeps comming back to me!!!

Subject:      Re: GETTY error
To:           Kenny McDonald <c60244@ccfiris.aedc>

Kenny,

We had similar "problems" here.  It was caused by people
using "nohup program.name &", then logging off...  Then those error
messages would start (ttyd45 if nohup was started from that port, etc).

SOOOOOOoooo I convinced my users to use "batch" instead to send
programs.  "batch" is MUCH better to use than "nohup" because:

   1. any output is sent to you via mail.

   2. it is much more efficient:  it runs at a lower priority than
      interactive jobs, so interactive users are NOT penalized.

   3. You can control the number of jobs running by changing
      the queue configuration files in /usr/lib/cron/queuedefs.
      You can also change the "nice" priority of the queues.

   4. This has worked very well in here.  When a large job (larger
      than a few minutes) is processed, "batch" is always used.
      (a few tried to do it in interactive mode, but "got caught"!).


Hope this helps,

     Claude Cantin
     National Research Council of Canada