topic Re: Command substitution in Operating System - HP-UX

Command substitution

Kevin.Wang — Mon, 21 Jul 2003 04:29:18 GMT

#TEST=$(DATE)
#echo $TEST
Mon Jul 21 13:23:59 EAT 2003
#set
........
TEST='Mon Jul 21 13:23:59 EAT 2003'
TZ=EAT-8
_=2003

how to delete VAR TEST when i execute set?

Re: Command substitution

Tim Adamson_1 — Mon, 21 Jul 2003 04:32:04 GMT

Hi,

Try the unset command

unset TEST

Cheers!

Re: Command substitution

Con O'Kelly — Mon, 21 Jul 2003 04:40:59 GMT

Hi

You can use
# unset
eg
# unset VAR.

Cheers
Con

Re: Command substitution

Rajeev Shukla — Mon, 21 Jul 2003 04:41:52 GMT

use
#unset

to unset the vaiable

Rajeev

Re: Command substitution

Con O'Kelly — Mon, 21 Jul 2003 04:44:46 GMT

Hi

You can use the unset command.
# unset
eg
# unset TEST

Cheers
Con

Re: Command substitution

Radim Jarosek — Mon, 21 Jul 2003 04:54:02 GMT

Hi,

try this :

# unset TEST

HTH

Radim

Re: Command substitution

twang — Mon, 21 Jul 2003 05:10:48 GMT

Use "unset TEST" in your script.

Re: Command substitution

nibble — Mon, 21 Jul 2003 05:14:48 GMT

try this

# unset TEST

Re: Command substitution

Caesar_3 — Mon, 21 Jul 2003 06:17:58 GMT

Hello Kevin!

What you need to do in shell is:
unset TEST

(unset )

Good luck.

Caesar

Re: Command substitution

John Meissner — Mon, 21 Jul 2003 10:23:55 GMT

you can use:

unset test

to unset a variable. you don't really need to unset this variable unless you are going to have your script read for this variable again. Basically by this I mean if you have your script do something and print the date along with your action.... and want the action to repeat... but with the current date printed each time with it.

you can also unset multiple variables at the same time if you wish to.

unset test1 test2 test3

regards

Re: Command substitution

Malleron Mathieu — Mon, 21 Jul 2003 13:37:23 GMT

omg you are doing that only for get some points ....

Re: Command substitution

John Collier — Fri, 25 Jul 2003 13:33:42 GMT

Malleron,

I don???t know about you, but I don???t see that post as being nothing more than an attempt to get some points. I personally feel that John was simply expanding on the issue above and beyond what the previous replies revealed. I know that there is a high possibility that some new ???Sys Admin in Training??? may very well be helped by the additional information provided as they search the forums for answers and/or knowledge.

Even if I am incorrect in my thoughts, I am personally more appalled at your attempt to slam a person publicly for any reason.

This is supposed to be a professional forum with professional people. Personally, I don???t feel that you are exhibiting very professional behavior when you make comments like that about other forumers.

That is, of course, just my own personal thoughts on the subject.

Have a nice day???

PS. I am not expecting, nor do I want, any points for this post. Please assign it a 0 (zero).

Re: Command substitution

Pete Randall — Fri, 25 Jul 2003 13:42:05 GMT

John,

You're seeing the cleaned up version of this thread. I don't even remember who it was but somebody had replied like 20 times and gotten 10 points for each one. And it was obvious that they weren't a "stuck submit key" syndrom, either, because there were other answers interspersed.

That's what the reference was about.

Pete

Re: Command substitution

John Collier — Fri, 01 Aug 2003 13:02:10 GMT

If that is truly the case, then I retract my statement.

I can only comment on what I see when I arrive, not what was there that I have never seen.

Please forgive me???

Re: Command substitution

John Meissner — Fri, 01 Aug 2003 13:28:02 GMT

unset etc....

unset test

this can be done for multiple variable at the same time.

regards,