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
F15449521: D16053.id38628.diff
Fri, Mar 28, 10:47 AM
F15434058: D16053.diff
Tue, Mar 25, 1:44 AM
F15414455: D16053.diff
Mar 20 2025, 12:38 AM
F15413452: D16053.id38626.diff
Mar 19 2025, 6:51 PM
F15388807: D16053.id38626.diff
Mar 15 2025, 4:26 AM
F15374400: D16053.diff
Mar 12 2025, 6:50 PM
F15338465: D16053.diff
Mar 9 2025, 11:00 AM
F15283346: D16053.diff
Mar 4 2025, 6:58 AM
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
Lint
Lint Not Applicable
Unit
Tests Not Applicable

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