Linux

Thank you.

Code:

PID=$

should be

Code:

PID=$!

I couldn't have seen that error without you posting your code.

Ok, here is the whole code with the change

#!/bin/bash
#Linux Script
file="`date +%b_%d_%y:%H:%M:%S`"

trap "kill $PID" EXIT
exec 2> ~/errors/idtoolerrorlogs/$file
tail -f ~/errors/idtoolerrorlogs/$file &
PID=$!


echo "`date +%D:%H:%M:%S`" ; read -p " User ID"= UserID

echo "`date +%D:%H:%M:%S`"
read -p "Enter Server(s)"= servertext
for i in $servertext
do
echo "$i"
echo "`date +%D:%H:%M:%S`"
ssh -t -t $i id $UserID



done


The results:

kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

So I use single quotes in the "kill" command.


#!/bin/bash
#Linux Script
file="`date +%b_%d_%y:%H:%M:%S`"

trap 'kill $PID' EXIT
exec 2> ~/errors/idtoolerrorlogs/$file
tail -f ~/errors/idtoolerrorlogs/$file &
PID=$!


echo "`date +%D:%H:%M:%S`" ; read -p " User ID"= UserID

echo "`date +%D:%H:%M:%S`"
read -p "Enter Server(s)"= servertext
for i in $servertext
do
echo "$i"
echo "`date +%D:%H:%M:%S`"
ssh -t -t $i id $UserID

tixuw #Also added this just to recreate an error

done



Well , the error was trapped in the "$file" but it not show up on the screen and I was still able to continue with the script. So, if this is as far as we can go then thank you very much for your help. This is my first time created a series of major scripts and this really showed me how much more I have to learn. But if there is another way to pull of looking at the error on the screen and putting in a file a the same time, please show me how. Thanks again.