15 Nov
2017
15 Nov
'17
7:22 p.m.
Mark Haney wrote:
On 11/15/2017 11:48 AM, m.roth@5-cent.us wrote:
Mark Haney wrote:
For the record, this was the only option to handle the task I'm having issues with inside cron.
Yes. Do not trust your environment, running as a cron job, to be what you think it is. Try testing it by have your cron job, at the top of the script, issue the env command.
I'm not sure I follow, where should the env command be placed? At the front of the cron line?
crontab -e 1 1 * * * run_my_script <save> Ok, I forget if you said it was perl or bash...
more run_my_script #!/bin/bash
env
<rest of script>
Is that clearer?
mark