"wrong" detection of service status

[shihira]

"wrong" detection of service status

[Shihira]

@andcoz Thank you so much for your report.

It seems to be a predictable behaviour. You can see core.js:139 to find out how it works. If you are eager for a work-around, you are recommended to try the more flexible type toggler and set command_on, command_off and detector based on your demand. And If you are willing to help me improve the extension, is there a properer grep regular expression that works for you? Maybe grep 'Active: activ[ei]' (i for "activing")?

[Shihira]

@andcoz Some slight changes are made in the latest commit a608c62 . Does it meet your demand? More feedbacks are welcome.

[andcoz]

I just pulled the latest version and It works like a charm. Thank you.

On my system, the Active: line of systemctl status changes as follow when i stop and then start again a service (that forks and exits):

   Active: active (exited) since Sun 2016-05-08 18:17:41 CEST; 56s ago
   Active: deactivating (stop) since Sun 2016-05-08 18:18:40 CEST; 3s ago
   Active: inactive (dead) since Sun 2016-05-08 18:18:48 CEST; 2s ago
   Active: activating (start) since Sun 2016-05-08 18:18:59 CEST; 2s ago
   Active: active (exited) since Sun 2016-05-08 18:19:07 CEST; 2s ago

So IMHO, the regex Active: activ[ei]should work well.