Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsh!wcs
From: wcs@cbnewsh.att.com (Bill Stewart 908-949-0705 erebus.att.com!wcs)
Newsgroups: comp.unix.sysv386
Subject: Re: verbose batch output on console
Message-ID: <1991Apr1.033336.25492@cbnewsh.att.com>
Date: 1 Apr 91 03:33:36 GMT
References: <918@fnx.UUCP>
Organization: AT&T Bell Labs Special Services Division
Lines: 20

In article <918@fnx.UUCP> root@fnx.UUCP (I/Ovations System Administrator) writes:
]As system load goes up, the reasonable thing to do would seem to be to
]start batching everything that doesn't require user interaction.  The
]trouble is that as soon as there are more than a few things in the
]queue, the console starts filling with messages printing every minute
]telling me that there are too many jobs to execute immediately and at
]is rescheduling for later (like one minute later).  I *KNOW* that,

Where does /etc/cron send its output on your system?  Stdout, or /dev/console?
If it's stdout, you could just redirect it somewhere else from /etc/rc*/*.
Alternatively, depending on what commands you're talking about, it
may be simpler to just nice them a lot.  I've built a troff queueing
system which used at/batch, since the number of processes generated
by zillions of complex troff pipelines was too high even though the
processes were niced; all the flak went into the cronlog file.
-- 
# Bill Stewart 908-949-0705 erebus.att.com!wcs AT&T Bell Labs 4M-312 Holmdel NJ
(Little Girl:) When I grow up, I want to be a nurse      } From this week's UFT
(Little Boy:)  When I grow up, I want to be an engineer  } radio commercial
.... guess the Political Correctness Police don't run NYC's teachers' union yet