Timeline for How to handle a missing environment variable set in `crontab`
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 20 at 20:01 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 | Put quotes where they're needed. Additional info |
| Jan 20 at 5:15 | comment | added | Kusalananda♦ | @Seamus It's in POSIX, so you can look there. | |
| Jan 20 at 4:22 | comment | added | Seamus | Just one other thing: Do you have a link to the GNU docs on this technique?... Is this it? | |
| Jan 20 at 3:54 | vote | accept | Seamus | ||
| Jan 20 at 3:53 | comment | added | Seamus | OK - thanks. I've just done a quick test using RUN_BY_CRON=${RUN_BY_CRON-""}. That seems to be all I need in my case. AFAIC, this is a correct answer --- and the accepted answer :) | |
| Jan 20 at 3:49 | comment | added | Stephen Harris | Yes; it's an example of a variable that wouldn't normally exist. | |
| Jan 20 at 3:27 | comment | added | Seamus | I'm guessing that your NOSUCHVARIABLE is supposed to represent the environment variable I set in the crontab: RUN_BY_CRON ??? | |
| Jan 20 at 1:04 | history | answered | Stephen Harris | CC BY-SA 4.0 |