Sponsored Content
Full Discussion: Shell variables problems
Top Forums Shell Programming and Scripting Shell variables problems Post 302356338 by aigles on Friday 25th of September 2009 07:50:39 AM
Old 09-25-2009
Please, show us how you have resolved the problem.
Something like that ?
Code:
              . ./file_of_env
              for wfile in `cat list_of_files`
              do
                 eval file=$wfile
                 if [ -f ${file} ]
                 then
                      .....
                  else
                     ......
                  file
              done

Jean-Pierre.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

C Shell problems

I am a newbies here and also dummies in csh language. I've been told from my frenz this forum is very useful site for Q&A about UNIX script. Can anyone in here just lead me to learn more about csh language with code example. tq (3 Replies)
Discussion started by: unknown2205
3 Replies

2. UNIX for Dummies Questions & Answers

Problems with sed and flat file variables

Hello All, It has been a loooooooooooong time since I had last used sed but decided to use it for a simple task I have . My goal is to use sed to read variables from a flat file then use those same variables in order to make some subsitutions. However what I am finding is that when the... (1 Reply)
Discussion started by: icalderus
1 Replies

3. Shell Programming and Scripting

Shell script problems to do

Does anyone know a good site to do shell script problems? (0 Replies)
Discussion started by: cleansing_flame
0 Replies

4. Shell Programming and Scripting

problems calling out variables in a loop

good afternoon forums. i have a problem that ive been trying to work out all morning and cant seem to get my head around it. what i have in my script is individual letters saved in different variables. so if the word unix was saved then 'u' would be stored in the variable 'wvar1' 'n' in 'wvar2'... (7 Replies)
Discussion started by: strasner
7 Replies

5. UNIX for Dummies Questions & Answers

Problems in shell

hiiii this is the first time for me here >>> but really i have some problems for answers these things also understanding... Can any one help me? Write a simple shell as given in class. Your shell, called shell will read input lines from standard input, parse them into a... (3 Replies)
Discussion started by: Ronald kabbi
3 Replies

6. Shell Programming and Scripting

Problems with expect and set variables

I'm writing a script that'll send a time-stamp to my backup server. I create a file with the name of the current date, send it to my server with scp and rm the file from the local computer. Individually these commands work fine and with a set name the expect scripts also work fine. The problem... (0 Replies)
Discussion started by: Ktesh564
0 Replies

7. Shell Programming and Scripting

Two problems when I am writing my own shell

Hi, guys: I am writing my own shell using c. I meet with two problems. First, when I use tcsetpgrp system call to move a background job to foreground, when this job finishes, my shell program also exit. What is the problem for that? Second, when I use signal , if the child has its own... (1 Reply)
Discussion started by: tomlee
1 Replies

8. Shell Programming and Scripting

Problems with variables syntax

Hi there I am really struggling :eek: to place a value in a variable with the following loop, having run out of ideas please can someone point me in the right direction? We first read two PIDs of a program (say calc) into an array, then we loop reading the details of those processes into a... (6 Replies)
Discussion started by: nathan.harris
6 Replies

9. Shell Programming and Scripting

Problems with substitution between two variables

To all geeks, What I want to achieve: 1. Accept two filenames from user and store the filenames in two variables (FILE1 and FILE2) 2. Check if files exisits. If doesn't, then exit 3. If files exist, look for a particular string in both files 4. If the string exists, then change the... (8 Replies)
Discussion started by: Deepak Tulsani
8 Replies

10. Shell Programming and Scripting

Problems with awk (fatal error) and paste (two variables into one column-by-column)

Hello, I have a script extracting columns of useful numbers from a data file, and manipulating the numbers with awk commands. I have problems with my script... 1. There are two lines assigning numbers to $BaseForAveraging. If I use the commented line (the first one) and let the second one... (9 Replies)
Discussion started by: vgbraymond
9 Replies
SED(1)							      General Commands Manual							    SED(1)

NAME
sed - stream editor SYNOPSIS
sed [ -n ] [ -e script ] [ -f sfile ] [ file ] ... DESCRIPTION
Sed copies the named files (standard input default) to the standard output, edited according to a script of commands. The -f option causes the script to be taken from file sfile; these options accumulate. If there is just one -e option and no -f's, the flag -e may be omitted. The -n option suppresses the default output. A script consists of editing commands, one per line, of the following form: [address [, address] ] function [arguments] In normal operation sed cyclically copies a line of input into a pattern space (unless there is something left after a `D' command), applies in sequence all commands whose addresses select that pattern space, and at the end of the script copies the pattern space to the standard output (except under -n) and deletes the pattern space. An address is either a decimal number that counts input lines cumulatively across files, a `$' that addresses the last line of input, or a context address, `/regular expression/', in the style of ed(1) modified thus: The escape sequence ` ' matches a newline embedded in the pattern space. A command line with no addresses selects every pattern space. A command line with one address selects each pattern space that matches the address. A command line with two addresses selects the inclusive range from the first pattern space that matches the first address through the next pattern space that matches the second. (If the second address is a number less than or equal to the line number first selected, only one line is selected.) Thereafter the process is repeated, looking again for the first address. Editing commands can be applied only to non-selected pattern spaces by use of the negation function `!' (below). In the following list of functions the maximum number of permissible addresses for each function is indicated in parentheses. An argument denoted text consists of one or more lines, all but the last of which end with `' to hide the newline. Backslashes in text are treated like backslashes in the replacement string of an `s' command, and may be used to protect initial blanks and tabs against the stripping that is done on every script line. An argument denoted rfile or wfile must terminate the command line and must be preceded by exactly one blank. Each wfile is created before processing begins. There can be at most 10 distinct wfile arguments. (1)a text Append. Place text on the output before reading the next input line. (2)b label Branch to the `:' command bearing the label. If label is empty, branch to the end of the script. (2)c text Change. Delete the pattern space. With 0 or 1 address or at the end of a 2-address range, place text on the output. Start the next cycle. (2)d Delete the pattern space. Start the next cycle. (2)D Delete the initial segment of the pattern space through the first newline. Start the next cycle. (2)g Replace the contents of the pattern space by the contents of the hold space. (2)G Append the contents of the hold space to the pattern space. (2)h Replace the contents of the hold space by the contents of the pattern space. (2)H Append the contents of the pattern space to the hold space. (1)i text Insert. Place text on the standard output. (2)n Copy the pattern space to the standard output. Replace the pattern space with the next line of input. (2)N Append the next line of input to the pattern space with an embedded newline. (The current line number changes.) (2)p Print. Copy the pattern space to the standard output. (2)P Copy the initial segment of the pattern space through the first newline to the standard output. (1)q Quit. Branch to the end of the script. Do not start a new cycle. (2)r rfile Read the contents of rfile. Place them on the output before reading the next input line. (2)s/regular expression/replacement/flags Substitute the replacement string for instances of the regular expression in the pattern space. Any character may be used instead of `/'. For a fuller description see ed(1). Flags is zero or more of g Global. Substitute for all nonoverlapping instances of the regular expression rather than just the first one. p Print the pattern space if a replacement was made. w wfile Write. Append the pattern space to wfile if a replacement was made. (2)t label Test. Branch to the `:' command bearing the label if any substitutions have been made since the most recent reading of an input line or execution of a `t'. If label is empty, branch to the end of the script. (2)w wfile Write. Append the pattern space to wfile. (2)x Exchange the contents of the pattern and hold spaces. (2)y/string1/string2/ Transform. Replace all occurrences of characters in string1 with the corresponding character in string2. The lengths of string1 and string2 must be equal. (2)! function Don't. Apply the function (or group, if function is `{') only to lines not selected by the address(es). (0): label This command does nothing; it bears a label for `b' and `t' commands to branch to. (1)= Place the current line number on the standard output as a line. (2){ Execute the following commands through a matching `}' only when the pattern space is selected. (0) An empty command is ignored. SEE ALSO
ed(1), grep(1), awk(1), lex(1) 7th Edition April 29, 1985 SED(1)
All times are GMT -4. The time now is 05:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy