Page MenuHomePhabricator

If the overseer can't update the PID file, just move on
ClosedPublic

Authored by epriestley on Jun 19 2017, 9:53 PM.
Tags
None
Referenced Files
F18946128: D18139.diff
Nov 11 2025, 7:34 PM
F18874661: D18139.id.diff
Nov 5 2025, 3:30 PM
F18870953: D18139.diff
Nov 4 2025, 8:07 PM
F18775660: D18139.id.diff
Oct 10 2025, 7:44 PM
F18752415: D18139.id.diff
Oct 4 2025, 3:12 PM
F18748347: D18139.diff
Oct 3 2025, 8:50 PM
F18580182: D18139.diff
Sep 11 2025, 2:44 AM
F18580142: D18139.diff
Sep 11 2025, 2:30 AM
Subscribers
None

Details

Summary

Ref T12857. This is a little murky, but this behavior seems clearly better.

When the disk is full, daemons may attempt to update their PID files and fail. When this happens, keep running rather than exiting.

Test Plan
  • Made Filesystem::writeFile() throw an exception unconditionally to simulate a full disk.
  • Ran bin/phd start.
  • Saw daemons exit immediately.
  • Applied patch, saw daemons stick around and do useful work instead.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jun 20 2017, 3:39 AM
This revision was automatically updated to reflect the committed changes.