Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Problems setting or exporting variable when using multiple commands from same line.
Top Forums Shell Programming and Scripting Problems setting or exporting variable when using multiple commands from same line. Post 302721433 by scottrif on Thursday 25th of October 2012 11:35:56 AM
Old 10-25-2012
Corona688,

Thanks very much for the explanation. This is subtle behaviour I of which I was not aware. I looked further into the scripts from which I based my test on that "seemed" to work and found that the second script (which was not sourced) does not do anything with variables that need to exist outside of the second temporary shell. That explains that!

Thanks again!
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Exporting variable from config file

Hi, I am exporting the environment variable from config file, but when I echo the variable it does not display any value. Here is the snippet of the code #!/bin/sh export ENVIRONMENT_ROOT_DIRECTORY="/cb/$ENVIRONMENT" echo $ENVIRONMENT_ROOT_DIRECTORY ${JAVA_HOME}/bin/java... (2 Replies)
Discussion started by: bhavnabakshi
2 Replies

2. Solaris

variable exporting

Hi, can anyone tell me the difference between the below two examples: Eg-1: # name=bravo # echo $bravo what would be the o/p Eg-2: # name1=jhonny # export name1 # echo $name1 what would be the o/p If the o/p's of both examples are the same then what is the use of the cmd export... (3 Replies)
Discussion started by: rahul_11d
3 Replies

3. Shell Programming and Scripting

Putting multiple sed commands on a single line

Hi, I want to make sed write a part of fileA (first 7 lines) to file1 and the rest of fileA to file2 in a single call and single line in sed. If I do the following: sed '1,7w file1; 8,$w file2' fileA I get only one file named file1 plus all the characters following file1. If I try to use curly... (1 Reply)
Discussion started by: varelg
1 Replies

4. Shell Programming and Scripting

Exporting my dynamical variable won't work?

Even though the idea "might" not be great I still wrote this piece of code to get practice.. Which means that it is the CODE that matters here. Anyways; The intension is to create a program(or do we call it script?) that searches recursively through a folder to find a file - stored in a... (4 Replies)
Discussion started by: Pesk
4 Replies

5. Shell Programming and Scripting

exporting variable

Hi All; I m working on a script and came across an issue ,to explain it briefly here is the sample code echo $HOSTNAME|while read IN; do var=`echo $IN|awk -F "-" '{print $2}'`; export var; echo $var; done now I get the value of $var but when it is out of the while loop it does not return... (3 Replies)
Discussion started by: maverick_here
3 Replies

6. Shell Programming and Scripting

Export command variable exporting problem

I have a txt file from which i am assiging a value to a variable using the code in script1 script1.sh export f=$(sed -n "/Freq *=/ s/.*= *//p" ${R_path}/output.txt) echo "$f" --------> this works in script2 ( which executes the script1) eval ./script1.sh if && ; then echo... (1 Reply)
Discussion started by: shashi792
1 Replies

7. UNIX for Dummies Questions & Answers

Multiple Commands on a Single Line

Hi There, I have a cronjob that executes a small script (few lines) that I am certain can be achieved in a single line. The functional objective is actually really simple; cmd var1 The '1' in 'var1' is actually derived from date (day of month) but the snag is when working with 1-9 I... (3 Replies)
Discussion started by: Random79
3 Replies

8. Shell Programming and Scripting

Grabbing top line of text in a file and setting it to a variable

If I have a txt file with test.txt somelineoftext and I want to set that line of text to variable in a script: so #!/bin/bash var='' becomes #!/bin/bash var='somelineoftext' (3 Replies)
Discussion started by: digitalviking
3 Replies

9. Shell Programming and Scripting

Setting a variable in a stream of commands

can someone help me with this? AgentDX=/tmp/tesfinal && cat final.enc | openssl aes-128-cbc -a -d -salt -k hello | sh the content of final.enc is a code. and in that code, the value of AgentDX is needed. however, i cant seem to find a way to allow the code to recognize that the variable... (4 Replies)
Discussion started by: SkySmart
4 Replies

10. Shell Programming and Scripting

Csh - how to combine multiple commands in one line

Hey everyone, I am working in an environment where the different users can use ksh or csh. My situation is that I need the same result with one single command line. I am searching for the real path the file is in. My ksh input and output ts2:ts2adm> cd $(dirname $(which sapcontrol)); pwd -P... (2 Replies)
Discussion started by: h1kelds
2 Replies

LEARN ABOUT NETBSD

devscripts.conf

DEVSCRIPTS.CONF(5)						File Formats Manual						DEVSCRIPTS.CONF(5)

NAME

       devscripts.conf - configuration file for the devscripts package

DESCRIPTION

       The  devscripts	package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack-
       ages.  Many of these have options which can be configured on a system-wide and per-user basis.

       Every script in the devscripts package which makes use of values from these configuration files describes the specific settings	recognised
       in its own manpage.  (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts
       | grep /usr/bin.)

       The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings.	They  are  written
       with  bash(1)  syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of
       the devscripts scripts.	Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded
       as equivalent to the default setting.

       All  variable  names  are  written  in  uppercase, and begin with the script name.  Package-wide variables begin with "DEVSCRIPTS", and are
       listed below, as well as in the relevant manpages.

       For a list of  all  of  the  available  options	variables,  along  with  their	default  settings,  see  the  example  configuration  file
       /usr/share/doc/devscripts/devscripts.conf.ex.   This  is  copied  to  /etc/devscripts.conf  when the devscripts package is first installed.
       Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack-
       age is upgraded.

       Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option.

PACKAGE-WIDE VARIABLES
       The currently recognised package-wide variables are:

       DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
	      These  variables	control  scripts  which change directory to find a debian/changelog file or suchlike, and some other miscellaneous
	      cases.  In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions  will  be	performed.
	      The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but
	      this list may change with time (and I may not remember to update this manpage).  Please see the manpages of individual  scripts  for
	      details of the specific behaviour for each script.

SEE ALSO

       devscripts(1) and /usr/share/doc/devscripts/README.gz.

AUTHOR

       This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>.

DEBIAN
								 Debian Utilities						DEVSCRIPTS.CONF(5)
All times are GMT -4. The time now is 03:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy