Cron
Time-based scheduling of recurring jobs, and the reasons scheduled jobs quietly stop working.
Cron is the traditional Unix scheduler: a table of times and commands, evaluated every minute. The name now stands loosely for any time-based job scheduling, including the various platform-specific successors.
Scheduled jobs fail more often than interactive commands, and nearly always for environmental reasons rather than logical ones. A scheduled job runs with a minimal environment: a short search path, no shell profile, no interactive session, and often a different working directory. A command that works when typed fails when scheduled because the program is not on the path, or because a credential lives in a profile that was never sourced.
They also fail silently by default. Output goes nowhere unless directed somewhere, so a job that has been failing nightly for months looks exactly like one that has been succeeding. Logging to a file, and — better — recording success somewhere observable, is what makes the difference. See Observability and Silent Failure.
The practical rules: use absolute paths, set the environment explicitly, log to a known location, make the job idempotent so a double run is harmless, and provide a way to trigger it manually so it can be tested without waiting for the schedule.
See also9
Truncation Bias
Reading a truncated result as if it were the whole result, so every counterexample is invisible.
Method28 connections
Daemon
A long-running background process managed by the operating system's service supervisor.
Systems & Tooling19 connections
Environment Variable
A named value in a process's environment, inherited by its children — the standard configuration channel.
Systems & Tooling23 connections
Fail Fast
Crash at the point of misconfiguration rather than degrading quietly into a wrong state.
Method27 connections
Secret Management
Storing, distributing, and rotating credentials without embedding them in code or history.
Systems & Tooling33 connections
Root Cause Analysis
Escalating past the visible symptom until you find the layer that actually produced it.
Method49 connections
Shebang
The "#!" line at the top of a script that tells the kernel which interpreter should run it, so a text file can be executed like a compiled program, and the portability traps around it.
Systems & Tooling11 connections
Background Agent
An agent run that continues without a person watching, started by a schedule, an event, or a handoff, and reports its results when done.
Agents & Language Models13 connections
Fake Clock
Replacing the real clock in tests with one the test controls, so time-dependent code can be checked at midnight, across DST, or after an hour of retries without waiting.
Testing & Verification9 connections
Linked from14
- Background AgentAgents & Language Models
An agent run that continues without a person watching, started by a schedule, an event, or a handoff, and reports its results when done.
- Code SigningSystems & Tooling
Cryptographically attesting who produced a binary, and the operating-system checks built on it.
- DaemonSystems & Tooling
A long-running background process managed by the operating system's service supervisor.
- ETL PipelineData & Content
The job of pulling data out of operational systems, cleaning and reshaping it, and loading it somewhere it can be analyzed, and the move from transforming before loading to transforming after.
- Exit StatusSystems & Tooling
The small number every process returns when it ends, zero for success and anything else for failure, and the conventions that let shells, CI systems, and init systems act on it.
- Fail FastMethod
Crash at the point of misconfiguration rather than degrading quietly into a wrong state.
- Fake ClockTesting & Verification
Replacing the real clock in tests with one the test controls, so time-dependent code can be checked at midnight, across DST, or after an hour of retries without waiting.
- IdempotenceSystems & Tooling
The property that performing an operation twice has the same effect as performing it once.
- Idle GamePlay & Games
A genre in which progress continues while the player is absent, built on exponential curves the player learns to read.
- ObservabilityMethod
How much of a system's internal state can be inferred from what it emits.
- ProcessSystems & Tooling
A running program with its own memory, environment, and identity.
- ShebangSystems & Tooling
The "#!" line at the top of a script that tells the kernel which interpreter should run it, so a text file can be executed like a compiled program, and the portability traps around it.
- SystemdSystems & Tooling
The dominant Linux init system, replacing sequential startup scripts with declarative, parallel, dependency-aware units.
- Time ZoneSystems & Tooling
Civil time is a political layer over solar time, and its rules change often enough to be data.