âšī¸ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0.3 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value |
|---|---|
| URL | https://docstore.mik.ua/orelly/unix3/upt/ch23_01.htm |
| Last Crawled | 2026-04-02 01:13:31 (9 days ago) |
| First Indexed | 2017-04-21 05:42:30 (8 years ago) |
| HTTP Status Code | 200 |
| Meta Title | Job Control (Unix Power Tools, 3rd Edition) |
| Meta Description | null |
| Meta Canonical | null |
| Boilerpipe Text | One cautionary note on job control: there's no such
thing as a free lunch. In other words, while Unix blithely lets you
put all the processes you want into the background, they all share
the same CPU, RAM, and hard drive resources. If one process dominates
one of these resources, the other processes won't
get done any faster than they would have had you run them one after
the other to completion. So if you've got a process
that's CPU-intensive (such as a photomosiac
program), there's little point in trying to run more
processes on that machine.
From the days of mainframes, when programs were submitted on stacks
of cards, comes the term "job
control." This chapter is going to go into some
depth about using your shell's job control features.
For those already familar with the concept, here is the thirty-second
version of "Job Control in a
Nutshell." |
| Markdown | [home](https://docstore.mik.ua/) \| [O'Reilly's CD bookshelfs](https://docstore.mik.ua/orelly/bookshelfs.html) \| [FreeBSD](https://docstore.mik.ua/manuals/freebsd.html) \| [Linux](https://docstore.mik.ua/manuals/linux.html) \| [Cisco](https://docstore.mik.ua/univercd/cc/td/doc/product/) \| [Cisco Exam](https://ciscoexam.online/)
***
| | | |
|---|---|---|
| | | |
| [](https://docstore.mik.ua/orelly/unix3/upt/part5.htm) | | [](https://docstore.mik.ua/orelly/unix3/upt/ch23_02.htm) |
| | | |
| [](https://docstore.mik.ua/orelly/unix3/upt/part5.htm) | [](https://docstore.mik.ua/orelly/unix3/upt/index.htm) | [](https://docstore.mik.ua/orelly/unix3/upt/ch23_02.htm) |
| V. Processes and the Kernel | [](https://docstore.mik.ua/orelly/unix3/upt/index/index.htm) | 23\.2. Job Control Basics |
*** |
| Readable Markdown | One cautionary note on job control: there's no such thing as a free lunch. In other words, while Unix blithely lets you put all the processes you want into the background, they all share the same CPU, RAM, and hard drive resources. If one process dominates one of these resources, the other processes won't get done any faster than they would have had you run them one after the other to completion. So if you've got a process that's CPU-intensive (such as a photomosiac program), there's little point in trying to run more processes on that machine.
From the days of mainframes, when programs were submitted on stacks of cards, comes the term "job control." This chapter is going to go into some depth about using your shell's job control features. For those already familar with the concept, here is the thirty-second version of "Job Control in a Nutshell."
|
| Shard | 76 (laksa) |
| Root Hash | 14228682706106458676 |
| Unparsed URL | ua,mik!docstore,/orelly/unix3/upt/ch23_01.htm s443 |