ENV vs BASH_ENV | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Hi all, I cannot find out the difference between defining the two variables, but I discovered after a lot that having both set up in my crontab avoids a script to run correctly. For instance if I have in my crontab: ENV=/home/luca/.profile BASH_ENV=/home/luca/.profile then a shell script seems not to execute unless its output is redirect to a file. So the line 00 10 * * * myBackup.sh does not seem to run (or starts and ends immediatly), while 00 10 * * * myBackup.sh > /tmp/backup.log works fine. If I run the backup script manually it works (it uses rsync). What's the magic around the above variables? Thanks, Luca -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Site Home] [Linux Newbie] [Audio] [Hams] [Kernel Newbies] [Memory] [Util Linux NG] [Security] [Netfilter] [Bugtraq] [Writing Drivers] [Photo] [Yosemite Photos] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux Device Drivers] [Samba] [Video 4 Linux] [Git] [Linux Resources] [Fedora Users]
![]() |
![]() |