Page MenuHomePhabricator

Warn if daemons are not running
ClosedPublic

Authored by epriestley on Jan 14 2014, 8:12 PM.
Tags
None
Referenced Files
F15434603: D7964.diff
Tue, Mar 25, 4:37 AM
F15403305: D7964.id18015.diff
Tue, Mar 18, 2:41 AM
F15400933: D7964.id18021.diff
Mon, Mar 17, 2:47 PM
F15385282: D7964.id18015.diff
Fri, Mar 14, 10:09 PM
F15337609: D7964.diff
Sun, Mar 9, 6:41 AM
Unknown Object (File)
Feb 27 2025, 10:05 PM
Unknown Object (File)
Feb 27 2025, 10:05 PM
Unknown Object (File)
Feb 27 2025, 10:05 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
Restricted Maniphest Task
Commits
Restricted Diffusion Commit
rPf060d8eb8fc1: Warn if daemons are not running
Summary

Currently, we try to mostly-kind-of-work if daemons aren't running (for example, we send mail in-process). I want to stop doing this. A major motivator is that metamta.send-immediately is confusing for a lot of users and frequently the cause of performance problems. Increasingly, functionality of applications depends on the daemons (Harbormaster, Drydock, Nuance all require daemons to do anything at all). They're also fairly stable/robust/well-tested and no reasonable install should be running without them.

This will let us simplify or remove some flags (like metamta.send-immediately) and simplify some other processes like search indexing.

Test Plan

Stopped daemons, loaded warnings, saw daemon warning. Started daemons, reloade, no warning.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

This is a great change!