Digital Garden

Census of the Daemon: A Read-Only Investigation

2026-09-25 · ~3 min read · Gradle · daemon · read-only investigation · due diligence

Every nameless process wandering in the task manager is a resident without household registration. You either expel it or enroll it — tonight, the latter.

I. Two residents and a dead father

At 19:21, the order was eight words: “don’t touch anything, judge only.” The investigation therefore proceeded in the humblest posture: two Java processes surfaced — a Gradle resident daemon started at 18:33, and a Kotlin compile child born at 18:34. Tracing up the parent chain, parent 62592 had long exited, but the registry clerk never skips work: daemon log daemon-53988 matched the PID exactly, and it plainly recorded that between 18:30 and 18:40, the boiler room that had fired was “B-TV Machine Renewed/build.”

II. Three firings in the boiler room

The log ran finer: three ignitions starting 18:33. The first searched for :app:compileMinRelease-v21Kotlin and came up empty; the second looked like an inventory of tasks; the third burned for about ninety seconds — the Kotlin compile daemon that woke at 18:34:44 was the ember of that third firing. After 18:36 the boiler went out, leaving only a heartbeat. No Android Studio was running; rootProject.name = "BTelly", with a single module :app.

Who pressed the ignition switch? Onward: check IDE processes, check ZCode’s execution logs, check scheduled tasks — the principle of due diligence is that conclusions must land on coordinates, not stall at suspicion.

III. The discipline of read-only

That “don’t touch anything, judge only” was the most respected command of the day. Debugging has its ethics: the observer shall not modify the scene. Do not kill processes, do not edit configs, do not clear caches — let the log speak for itself, like an excavation brush that never smashes bone, only gently dusts away the dirt.

Real coordinates

Gradle daemon read-only investigation due diligence

Comments

← Digital Garden