Re^4: Environment Variables?????

Just set up an environment for the cron job that has all the information (and permissions and so on) it needs to run properly. I bet a lot of your personal environment information consists of stuff such as a customised PATH, a prompt (likely PS1, PS2 etc), maybe something to tell Perl to look into a directory in your HOME to look for modules (e.g. PERL_LIB = ~/perl5lib), maybe some stuff to auto-beautify the output of the ls command, yadayadayada. Does the cron job really need all that? Or could it live a happy life with just a minimal environment?

Comment on Re^4: Environment Variables?????

Replies are listed 'Best First'.
Re^5: Environment Variables????? by mrguy123 (Hermit) on Jun 27, 2012 at 13:32 UTC
I agree with you that my private environment information (which is alarmingly similar to what you described) is not very relevant for the cron job. In my case, however, I am working on a product where there are close to a 100 "public" env variables which are used widely in every program (they are stored in a different .cshrc file which is sourced by my private one). Therefore, the idea of updating a separate file each time I need to use a different env variable seems like a recipe for mistakes. So, do you think there is there an "in-between" solution or do we agree to disagree?	[reply]
Re^6: Environment Variables????? by muba (Priest) on Jun 27, 2012 at 13:37 UTC
Alarmingly? Not so much. It's pretty much your typical set-up :) There is an in-between solution, kindly suggested by roboticus below.	[reply]
Re^7: Environment Variables????? by mrguy123 (Hermit) on Jun 27, 2012 at 13:43 UTC
Thanks! BTW, I meant "alarmingly" in good humor, but putting emoticons in parentheses in not so simple :)	[reply]
Re^8: Environment Variables????? by Anonymous Monk on Jun 27, 2012 at 13:55 UTC