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
F19801500: D15782.diff
Sat, Feb 28, 11:53 PM
F19800268: D15782.diff
Sat, Feb 28, 2:04 PM
F19755628: D15782.diff
Tue, Feb 17, 5:18 PM
F19660834: D15782.id38022.diff
Feb 7 2026, 4:49 AM
F19504455: D15782.id38023.diff
Jan 9 2026, 5:11 AM
F19504407: D15782.id38023.diff
Jan 9 2026, 5:09 AM
F19219346: D15782.id38022.diff
Dec 17 2025, 9:54 AM
F18890851: D15782.id.diff
Nov 7 2025, 10:00 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.