fix(systemd): ensure isRunning accounts for activating status as well

acburdine · acburdine · commit 0f20c6feef62 · 2017-07-06T02:12:38.000-04:00
no issue
- if Ghost hasn't quite started yet (or didn't start due to an error) then systemd will be in the "activating" state
diff --git a/extensions/systemd/systemd.js b/extensions/systemd/systemd.js
@@ -72,7 +72,8 @@ class SystemdProcessManager extends cli.ProcessManager {
             return true;
         } catch (e) {
             // Systemd prints out "inactive" if service isn't running
-            if (!e.message.match(/inactive/)) {
+            // or "activating" if service hasn't completely started yet
+            if (!e.message.match(/inactive|activating/)) {
                 throw e;
             }
 

Original file line number	Diff line number	Diff line change
`@@ -72,7 +72,8 @@ class SystemdProcessManager extends cli.ProcessManager {`
`72`	`72`	`return true;`
`73`	`73`	`} catch (e) {`
`74`	`74`	`// Systemd prints out "inactive" if service isn't running`
`75`		`- if (!e.message.match(/inactive/)) {`
	`75`	`+ // or "activating" if service hasn't completely started yet`
	`76`	`+ if (!e.message.match(/inactive\|activating/)) {`
`76`	`77`	`throw e;`
`77`	`78`	`}`
`78`	`79`