Page MenuHomePhabricator

Send the `aphlict` process log to the `node` log
ClosedPublic

Authored by epriestley on Apr 22 2016, 12:01 AM.
Tags
None
Referenced Files
F18890851: D15782.id.diff
Fri, Nov 7, 10:00 AM
F18877319: D15782.id38023.diff
Thu, Nov 6, 7:27 AM
F18869092: D15782.diff
Tue, Nov 4, 9:52 AM
F18856363: D15782.diff
Sat, Nov 1, 9:24 AM
F18816480: D15782.id38022.diff
Oct 21 2025, 7:12 AM
F18807795: D15782.id38023.diff
Oct 19 2025, 3:28 AM
F18766492: D15782.diff
Oct 7 2025, 4:57 PM
F18764160: D15782.id38023.diff
Oct 7 2025, 4:35 AM
Subscribers
None

Details

Summary

I've possibly seen a couple of aphlict processes exit under suspicious circumstances (maybe?). Make sure any PHP errors get captured into the log.

Test Plan
  • Added an exception after forking.
  • Before change: vanished into thin air.
  • After change: visible in the log.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Send the `aphlict` process log to the `node` log.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • Also print more diagnostic information about signals.
chad edited edge metadata.
This revision is now accepted and ready to land.Apr 22 2016, 12:43 AM
This revision was automatically updated to reflect the committed changes.