You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it's not possible to use have commands that use the shell capabilities. For example, it's not possible to wrap completely the following command with cron-sentry:
ls /dir | mycommand
With cron-sentry it would be possible to wrap the ls /dir part, but not the whole thing (unless cron-sentry is executed twice). So, if the ls command works, but mycommand fails, cron-sentry wouldn't catch it.
The above is true for |, ||, &&, >, >>, etc.
The text was updated successfully, but these errors were encountered:
In short, call() should be passed shell=True if there is exactly one token in the command line. In that case raven-cron "foo | bar" would honour the pipe. The bug in the original library was actually the opposite: they used shell=True with multiple tokens, e.g. raven-cron foo bar baz, with the result that the extra token were ignored.
Currently it's not possible to use have commands that use the shell capabilities. For example, it's not possible to wrap completely the following command with cron-sentry:
ls /dir | mycommand
With cron-sentry it would be possible to wrap the
ls /dir
part, but not the whole thing (unless cron-sentry is executed twice). So, if thels
command works, butmycommand fails
, cron-sentry wouldn't catch it.The above is true for
|
,||
,&&
,>
,>>
, etc.The text was updated successfully, but these errors were encountered: