Storing lines of output into a script variable

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Passing variable as input & storing output in other variable

I have a below syntax its working fine... var12=$(ps -ef | grep apache | awk '{print $2,$4}') Im getting expected output as below: printf "%b\n" "${VAR12}" dell 123 dell 456 dell 457 Now I wrote a while loop.. the output of VAR12 should be passed as input parameters to while loop and results...

2. Shell Programming and Scripting

Storing command output in a variable and using cut/awk

Hi, My aim is to get the md5 hash of a file and store it in a variable. var1="md5sum file1" $var1 The above outputs fine but also contains the filename, so somthing like this 243ASsf25 file1 i just need to get the first part and put it into a variable. var1="md5sum file1"...

3. Shell Programming and Scripting

Storing lines of a file in a variable

i want to store the output of 'tail -5000 file' to a variable. If i want to access the contents of that variable, it becomes kinda difficult because when the data is stored in the variable, everything is mushed together. you dont know where a line begins or ends. so my question is, how can i...

4. Shell Programming and Scripting

sed not storing output in shell script

Hello, Following my learning of shell scripting.. I got stuck yet again. If I execute this command on terminal: $ sed "s/off/on/g" file > fileAUX I successfully change the text off to on from file to fileAUX. But the same command is not working inside a shell script. I tested and...

5. Shell Programming and Scripting

Storing output into a variable

My script below seems to be choking because I need the the output of the find command to be stored as a variable that can then be called by used lower in the script. #!/bin/bash cd "/resumes_to_be_completed" var1=find . -mmin -1 -type f $ -name "*.doc" -o -name "*.docx" $...

6. Shell Programming and Scripting

storing output from echo & cut into variable

Hi All, Hope someone can advise here as I have been struggling to find a syntax that works here. I have tried a stack of combination I have seed in the forums but I think because I have needed to use "" and `` in the statments another method is found. I am reading in lines with the following...

7. UNIX Desktop Questions & Answers

problem while storing the output of awk to variable

Hi, i have some files in one directory(say some sample dir) whose names will be like the following. some_file1.txt some_file2.txt. i need to get the last modified file size based on file name pattern like some_ here i am able to get the value of the last modified file size using the...

8. Shell Programming and Scripting

Using 'defaults read' and storing the output in a variable

Hi all, I'm creating a script which uses 'defaults read' to retrieve details from an Info.plist like this; defaults read "/Path/Contents/Info" CFBundleShortVersionString This works fine in Terminal and returns the expected values. Is it possible to use this command in a script, and...

9. UNIX for Dummies Questions & Answers

Storing the output into a variable

Hi unix gurus, I am trying to store the result of a command into a variable. But it is not getting stored. x='hello' y=echo $x | wc -c but it is giving the output as 0(zero) Pls help me its very urgent

10. Shell Programming and Scripting

storing output of awk in variable

HI I am trying to store the output of this awk command awk -F, {(if NR==2) print $1} test.sr in a variable when I am trying v= awk -F, {(if NR==2) print $1} test.sr $v = awk -F, {(if NR==2) print $1} test.sr but its not working out . Any suggestions Thanks Arif

LEARN ABOUT SUSE

makesh

MAKESH(1)                                                     General Commands Manual                                                    MAKESH(1)

NAME

       makeSH - a .SH script maker

SYNOPSIS

       makeSH files

DESCRIPTION

       MakeSH  examines  one or more scripts and produces a .SH file that, when run under sh, will produce the original script.  The .SH script so
       produced has two sections containing code destined for the output.  The first section has variable substitutions performed  on  it  (taking
       values  from  config.sh), while the second section does not.  MakeSH does not know which variables you want to have substituted, so it puts
       the whole script into the second section.  It's up to you to insert any variable substitutions in the first section for any values you want
       from config.sh.

       You  should  run  makeSH from within your top-level directory and use the relative path to the file as an argument, so that the "Extracting
       ..." line printed while running the produced .SH file later on will give that same path.

AUTHOR

       Larry Wall <lwall@netlabs.com>

SEE ALSO

       pat(1), metaconfig(1), makedist(1).

BUGS

       It could assume that variables from metaconfig's Glossary need to be initialized in the first section, but I'm too lazy to make it do that.

                                                                       LOCAL                                                             MAKESH(1)

UNIX for Dummies Questions & Answers