From: Luca Ferrari <fluca1978@infinito.it>
To: linux-admin@vger.kernel.org
Subject: ENV vs BASH_ENV
Date: Mon, 21 Jul 2008 17:58:23 +0200 [thread overview]
Message-ID: <200807211758.24073.fluca1978@infinito.it> (raw)
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
next reply other threads:[~2008-07-21 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 15:58 Luca Ferrari [this message]
2008-07-21 16:16 ` ENV vs BASH_ENV Axl Purushu
2008-07-22 12:14 ` Luca Ferrari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807211758.24073.fluca1978@infinito.it \
--to=fluca1978@infinito.it \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).