Page MenuHomePhabricator

Warn if daemons are not running
ClosedPublic

Authored by epriestley on Jan 14 2014, 8:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 19, 6:17 PM
Unknown Object (File)
Wed, Dec 18, 10:51 AM
Unknown Object (File)
Sun, Dec 15, 8:22 AM
Unknown Object (File)
Sat, Dec 14, 5:27 PM
Unknown Object (File)
Fri, Dec 13, 7:43 AM
Unknown Object (File)
Wed, Dec 11, 7:10 AM
Unknown Object (File)
Tue, Dec 10, 2:22 AM
Unknown Object (File)
Sun, Dec 8, 12:20 AM
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!