Joseph Huckaby

It will be implemented in Cronicle v2 (Orchestra), which will be released this year (2023).

I do apologize, but I cannot reproduce this issue. I have CentOS 7.5.1804, Node.js v12.13.0, and Cronicle v0.8.32. The Shell Plugin works just fine when configured to run as other...

Unfortunately no, that's a static utility that has no access to the debug logger. Just out of curiosity, what does this command output for you, when executed on your Cronicle...

That is really very bizarre. That code simply shells out to `/usr/bin/getent` on Linux and returns the results. I cannot fathom how this is not working on your server. It's...

Cronicle is configured to install the [latest pixl-tools package version](https://github.com/jhuckaby/Cronicle/blob/master/package.json#L48). So it really depends on when you installed your Cronicle software. If you installed it anytime after the pixl-tools change,...

Check the Cronicle logs, especially the `WebServer.log`. It should have more information on why it is sending back a HTTP 400.

I don't know what to tell you, @streightedge. It works fine for me: ``` jhuckaby@joework temp $ cat run.json { "id": "eilhcggvv01" } jhuckaby@joework temp $ jhuckaby@joework temp $ curl...

I'm terribly sorry, but this is not possible with the current version of Cronicle v1. However, it will be a feature in Cronicle v2 (Orchestra), coming later this year.

@mikeTWC1984 Haven't decided yet. Was considering ticking the scheduler every second, but optimizing by skipping all events that don't use seconds, except on the minute tick.

Could be output buffer autoflush? See https://github.com/jhuckaby/Cronicle/issues/364