command not found yields exit code zero

[jautz]

With execbeat version 3.1.1 on GNU/Linux exit code zero is being returned if the configured command cannot be found.

The log file contains an appropriate error message but in the produced document the exitCode suggests success:

  "exec": {
    "command": "FILE",
    "exitCode": 0,
    "stdout": ""
  },

Please consider producing code 127 in this case because this will help to recognise the problem's cause. Thank you.

[christiangalsterer]

Thanks for reporting, will fix it in the next days.

…

On 17.03.2017, at 15:45, Joachim Jautz ***@***.***> wrote: With execbeat version 3.1.1 on GNU/Linux exit code zero is being returned if the configured command cannot be found. The log file contains an appropriate error message but in the produced document the exitCode suggests success: "exec": { "command": "FILE", "exitCode": 0, "stdout": "" }, Please consider producing code 127 in this case because this will help to recognise the problem's cause. Thank you. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[christiangalsterer]

A fix is a available on master. Will try to make a release soon.

[christiangalsterer]

Released with 3.2.0