Configuring a start‑up timeout for runit services in Artix Linux

The goal is to guarantee that a runit‑supervised service that hangs in its exec command is automatically terminated after a configurable interval, preventing it from consuming CPU or memory indefinitely on a low‑traffic VPS.

However, the base‑runit metapackage does not define a documented, enforceable timeout for service start‑up scripts; runit will wait indefinitely if the exec command blocks, and the official documentation does not describe a global mechanism to impose such a limit.

It remains unclear whether a single runit configuration file can be applied to all supervised services to enforce a timeout, or if each service must be individually wrapped (e.g., with a timeout helper) and how this interacts with existing Artix packages that already ship runit log directories.

What is the recommended way to apply a uniform start‑up timeout across all runit services without modifying each package’s runit script? Does Artix provide or plan to introduce a global timeout setting for runit, or must administrators rely on external wrappers and accept the maintenance overhead?