Shell Programming and Scripting

Not sure if I understood your requirements correctly, but this should do the job:

Code:

sed -nr '/chuser \"gecos=/ s/skipping: |\(TESTMODE\)//gp' modify.LOG | sort -u | tee /dev/tty | sh

You could use ksh or bash as well to execute the commands. Supplying it the -x option would eliminate the need for the tee step.

/dev/tty can become problematic.
Also I have seen bugs with ksh -x so I recommend

Code:

... | ksh -v

For lines that simple -- no evaluation, natural splitting on spaces -- I don't think you need to feed it into sh. The shell's own natural splitting should take care of it once you have it.

Code:

# VAR="echo asdf;qwerty something else"
# $VAR
asdf;qwerty something else

#

Thank you. Brilliant solution, unfortunately sed in ksh does not know the -r option. How could that sed command look instead? I'm trying now quite a while without success.

Has nothing to do with ksh, it's the version of sed on your system.

My try at it:

Code:

awk '{ gsub(/(^skipping: )|( ipsec \(TESTMODE\))|"/, ""); } 1' inputfile | while read LINE
do
        # Remove the 'echo' once you've tested and found it does what you ant.
        echo $LINE
done

Use nawk on Solaris.

In principle you can use any process which output are code-lines and pipe that in ksh (or any other shell i know, for that matter):

Code:

typeset -i iCnt=0

while [ $iCnt -le 10 ] ; do
     print - "echo foo $iCnt bar"
     (( iCnt += 1 ))
done | ksh

Notice, however, that there are certain things to be aware of:

First, your lines have to observe the line-length limit the system is compiled with. This is always the case but when writing lines of code you notice extraordinary long lines more easily than when you generate them.

Code:

typeset -i iCnt=0

var="echo "
while [ $iCnt -le <some-big-number> ] ; do
     var="$var $iCnt"
     (( iCnt += 1 ))
done
print - $var | ksh

This will eventually break for either the line "var="$var $iCnt" being too long, the number of maximum arguments being exceeded or the maximum commandline length being exceeded. Which of these events will happen first and at which value of some-big-number depends on your system, the version, etc..

Another possible problem is possible multiple interpretations of your commandline by a shell. Consider a try to execute a command on several selected hosts:

Code:

sed '.....' /some/raw/listofhosts |\
while read chHost ; do
     print - "ssh user@$chHost /some/command"
done | ksh

In this form it would work, because the commandline will not change with several shells interpreting it, but how about a command which should receive several parameters, some of them containing spaces:

Code:

ssh user@host /some/command "first arg" "second arg"

This will work on the commandline, but in your script-constructing script you would have to do:

Code:

sed '.....' /some/raw/listofhosts |\
while read chHost ; do
     print - "ssh user@$chHost /some/command \"first arg\" \"second arg\""
done | ksh

I hope this helps.

bakunin

Try

Code:

sed -n '/chuser \"gecos=/ s/skipping: \|(TESTMODE)//gp' modify.LOG | sort -u | sh -vx