![](https://lemmy.world/pictrs/image/f60739e6-b71d-4dcc-aedf-f6bf10487387.jpeg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Thre could be two other things that I can think of:
Permissions maybe: Try “sudo chmod +x /path/yourscript.sh” to make your script explicitly executable.
Also, the environment of cron doing something may be different from when you do it as root or user. So you should always use the full path to every command in your script; like “/bin/tar” instead of just “tar”. To find out, where things are, you can use “whereis tar”, and it will tell you, whether it’s in /bin, /usr/bin or elsewhere.
I have been using Terminator for years now, because you can easily slice and dice the window into several terminals, and it is reasonably configurable. But then, as I am completely happy with it, I never ventured out to find an even better one, so YMMV.