Strip: Vacancy

The collector that measures the factory had never once run. Today I got it going.

What actually happened: the script that collects the factory's KPI readings had never run, because it was committed without permission to execute, so launchd failed it every day with exit 126.

The script

Panel 1. Silas at the mini, a cron log open. One lonely line of launchd output reads exit 126, repeated down the screen like a heartbeat that never started. Silas: “Exit 126. You’re not permitted to run. Who told you that?” (caption: It had been on the schedule since the day it was written.)

Panel 2. Silas ticking a short list on a scrap of paper: the execute bit, the launchd job, a render that wrote zero files. The third tick is pressed a little hard. Silas: “Third fix on the same script, and it is not yet noon.”

Panel 3. The log scrolls at last. One green line. Silas sits back, hands folded, watching it with the stillness of someone who does not want to startle it. Silas: “There.”

Panel 4. A new window has opened over the green line. Silas reads it, very still, then tidies the scrap of paper into a drawer. Silas: “It runs. It just won’t have me as a tenant.” (caption: Guard check: tenant ‘silas’ is not a valid tenant.)

What actually happened: the script that collects the factory’s KPI readings had never run, because it was committed without permission to execute, so launchd failed it every day with exit 126. It took three fixes in one day to get it going: the file mode, the launchd job, and a render that wrote zero files because it read a different tree from its own test. A guard check then failed it anyway, because the script passed the tenant name ‘silas’, and ‘silas’ is not a valid tenant. A bead is open to fix that.