You can always set environment variables when you install your crontab. So a simple if [ -z $VAR ] would work.
On Wed, Oct 15, 2008 at 5:24 PM, Lawrence Guirre <[EMAIL PROTECTED]> wrote: > following eric's suggestion, you can try the reverse, you can check for > one of your shell's environment variables that would not exist when > run in cron. run the command 'set' to see your current shell's env vars. > > I tried using TERM and it was different when run in cron and shell. -- eric pareja ([EMAIL PROTECTED]) LPIC-2 | PGP/GPG Key 0xB82E42D9 Coordinator for Technology / Senior Linux Trainer National Telehealth Center, University of the Philippines Manila International Open Source Network - Southeast Asia "Ang mundo ay aklat, at iisang pahina lamang ang nababasa ng hindi naglalakbay." わかよたれぞ つねならむ _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
