root@fnx.UUCP (I/Ovations System Administrator) (03/28/91)
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, that's why I used batch in the first place. TFM is no help. Is there anyway to turn off these messages from 'at'? ISC 2.0.2
wcs) (04/01/91)
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