magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

process-poll

A deny rule: it refuses a process table inspected to wait on magus work the lock already reports, and names what to run instead.

What it catches

A process table inspected to wait on magus work the lock already reports.

Why

A magus run holds a project lock and announces itself, and magus status --watch=15s reads that same lock state continuously: holder PID, command, age. pgrep, pidof and ps invent a poll with no bound of its own that answers a question the lock message already answered.

Seeing it

A verdict names its rule in brackets, which is how you got here:

deny [process-poll]: ...

magus describe rule process-poll prints the same entry at a terminal, and magus describe rules lists every rule this workspace enforces.

See also

  • All rules - what this workspace enforces, deny first
  • The guard - how a verdict is reached and wired
guardrulesprocess-polldeny
Last updated (52c9a227)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. See workspace.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.