very interesting especially about the command variables, what an efficient way to override defaults and experiment without messing up your env or having to relog, that will be super useful. Does there exist a way to set multiple vars going in? ( also, the idea that you have to export variables out into the bigger context seems largely missing from the Windows experience, I guess bc of the workstation model, so i think it's general purpose and necessity mystifies a lot of ppl. its just something they stumble into and then copy paste to resolve, never knowing why. its always good to clarify the 'unix way' ) thanks again
In crontab itself. If you try, as root, systemctl edit sshd -- this will open in nano, use the variable to open in vim. You can also use the editor variable to set nano or any other variable
Thanks. Informative indeed.
very interesting especially about the command variables, what an efficient way to override defaults and experiment without messing up your env or having to relog, that will be super useful. Does there exist a way to set multiple vars going in? ( also, the idea that you have to export variables out into the bigger context seems largely missing from the Windows experience, I guess bc of the workstation model, so i think it's general purpose and necessity mystifies a lot of ppl. its just something they stumble into and then copy paste to resolve, never knowing why. its always good to clarify the 'unix way' ) thanks again
In CentOS 8.1 I don't see EDITOR variable set, yet when I try crontab -e I see it uses vim. Where is this configured?
In crontab itself. If you try, as root, systemctl edit sshd -- this will open in nano, use the variable to open in vim. You can also use the editor variable to set nano or any other variable
How to get in touch
You just did