essay
medium
Understand
job-vs-process
2 points
Question 19. CSCD240-E1-A
Define what a job is and explain how jobs differ from processes.
Work the drill
Answer on paper or in a terminal before revealing the ideal answer.
Ideal answer
A job is a shell-level abstraction for a command or pipeline, tracked by the shell with a local job ID (%1, %2). A job may comprise multiple processes. Jobs are visible only to the shell that started them (via jobs); processes are kernel-level, globally visible via ps.
Misconception bank
Each row below is a plausible wrong answer, the thinking that produces it, and the remedy that corrects the misconception. These are the foundation of the multiple-choice framing and the targeted feedback a student receives after answering.
A job = a process
Misconception. Conflates the two — very common.
Remedy. Highlight concrete differences: scope (shell vs kernel), ID (%1 vs PID).
A job is a cron job
Misconception. Different "job" concept — cron job is a scheduled task.
Remedy. Distinguish context: shell job control vs cron job. Both called "jobs."
Authority mappings
Hover any chip for the mapping justification; click to open the authority record.
DCWF roles:
IT-451 System Administrator
DCWF tasks:
T0501
NCAE errors:
SSH Login / failure: Failed to connect to host: IPSSH Login / partial: The following users failed t.SSH Login / partial: The following users failed t.
Course-artifact links
Lectures
- CSCD240-S26-L08. Pipes, filters, grep, sort, uniq, wc, tar
Lab questions
- CSCD240-S26-LAB6: Run a long command with &. Use jobs, fg, bg.