I use the shell execute plugin to retrieve statistics from my nas which my not be running. In this case all commands fail and produce an error log. I tried using 2> /dev/null to prevent it from logging but it doesn’t help. I know that usually an error should be logged but in this instance it is a expected behavior. It would be nice if I could specify per device if it should fail silently.
-
Silent mode for "pimatic-shell-execute"
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
you could try
> /dev/null 2>&1at the end of your Execute command…
Also try to disable the “Log Action Executing” ! -
@Stokstaart The rule execution will still log an error if the executed shell command fails. A work around may be to add another dummy command at the end of the command sequence to return a normal execution status (result 0) in all cases. However, I think the anticipated silent mode is certainly the better way of doing this.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig Right! I do this the other way around, i let my NAS send the stats to the API…
Still a silent fail option would be a great addition…!!
