Re: [OT] Screen (was Affecting Inst. Change)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/11/07 12:49, s. keeling wrote:
> Ron Johnson <ron.l.johnson@cox.net>:
>> Yes, but competent OSs have batch queues for running such jobs. Why
>> Unix has never had such a capability is beyond my understanding.
>
> man batch: at, batch, atq, atrm - queue, examine or delete jobs for
> later execution.
>
>> (NO!! cron is *not* an adequate substitute for batch queues!)
>
> cron's for regularly repeated jobs. batch and at are for sequential
> job scheduling.
How do you create more queues than just "b"?
How do you limit the number of batch jobs that can run at any one
time? (If the "job limit" of a queue is 4 and you submit 20 jobs,
the first 4 jobs grab the execute slots, and the remaining 16 wait
until execute slots open up.)
How do you tell one job to synchronize on another (i.e., sleep until
the "other" job is complete, and then continue with your own processing.
> I was running simulations with them in OSF/1 batch
> queues in the early '90s.
DEC OSF/1, you say? I bet that it took queue management concepts
from OpenVMS.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGRPIGS9HxQb37XmcRAm9YAKDuprKQH0LvJlnhGPr9RIzI+j53lQCdE80j
tOxY4zEdbqiCniKKTSBT7GQ=
=3Hd0
-----END PGP SIGNATURE-----
Reply to: