Page MenuHomePhabricator

Log when daemons trigger a reload in response to config changes
ClosedPublic

Authored by epriestley on Jun 6 2016, 1:34 PM.
Tags
None
Referenced Files
F19518099: D16053.id38626.diff
Thu, Jan 15, 5:50 PM
F19518098: D16053.diff
Thu, Jan 15, 5:50 PM
F19126088: D16053.id38628.diff
Dec 10 2025, 2:29 AM
F19119841: D16053.diff
Dec 9 2025, 9:26 PM
F19074645: D16053.id38628.diff
Dec 1 2025, 6:15 AM
F19043389: D16053.id38626.diff
Nov 26 2025, 9:53 PM
F18955027: D16053.diff
Nov 12 2025, 8:25 PM
F18883212: D16053.diff
Nov 6 2025, 11:45 PM
Subscribers
None

Details

Summary

Ref T10811. This puts an explicit message in the log when a module triggers a reload.

  • Also, lift declare(ticks = 1) up to top level.
  • Make sure verbose messages hit the disk log, not just the database log.
Test Plan

Ran daemons, changed config, saw them reload automatically with an explicit message.

Diff Detail

Repository
rPHU libphutil
Branch
daemon1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 12497
Build 15841: Run Core Tests
Build 15840: arc lint + arc unit

Event Timeline

epriestley retitled this revision from to Log when daemons trigger a reload in response to config changes.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Jun 6 2016, 1:36 PM