Next message: Jeff Hunsinger: "Re: [LUNI] OT: Soldering Irons..."
Sorry I already seemed to have really deleted any prior stuff you wrote on
this but U* scripts usually declare env. variables in upper case, not that
this is necessary but a good way to identify them from other code. You
reference them in your code by prefixing a '$' sign as in:
ENV_VAR = something
echo $ENV_VAR
The shell will first replace the reference with the env. variables contents
similarly as the single quote is doing, but not evaluating in this case. I
don't know for sure but bash may have more complex variable substitution
with ${} syntax of supplying default values if there is no initial value
set!
HTH,
Pat
Andrew Close wrote:
> i got the date thingy to work.
>
> mv .../logfile .../RotateLogs/logfile.`date
> '+%m_%d_%y'`
>
> i guess the `stuff` executes a command line statement
> in the middle of your string...? pretty cool.
>
> i'm still working on the env variable stuff though. ;)
>
> andy
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
> -=-
> Linux Users Of Northern Illinois: General Discussion Mailing list.
> For unsubscription, archives, and announcements only see http://luni.org
--
Patrick R. White
email: patwhite@interaccess.com
-=-
Linux Users Of Northern Illinois: General Discussion Mailing list.
For unsubscription, archives, and announcements only see http://luni.org
This archive was generated by hypermail 2b29
: Fri Mar 23 2001 - 23:21:56 CST