Shell Programming and Scripting

Bonjour,

I have a large script with a lot of print statements and misc commands. Standard and error outputs are redirected like into the following code :

Code:

#!/usr/bin/ksh

LOG=/<some dir>/log
> $LOG
exec >>${LOG} 2>>${LOG}

print aaaaa
print bbbbb
print ccccc
...
some_cmd

That way, standard and error outputs are added to the log file without appending >> {LOG} 2>>{LOG} after each print statement or command.

But now, we must execute these scripts via a new scheduler (VTOM) and still keep our ${LOG} file feeded.
The problem is that VTOM feeds its own logs with standard and error outputs so exec ... line must be commented.

My question : is there anyway to keep standard and error outputs alive for VTOM usage and feed too our UNIX log without appending redirections after each print statements and commands ?

ps : i've searched around tee command but without any good results. Maybe additional file descriptors may be used, but i've never worked with them.

Do you mind explaining me what was wrong with just:

Code:

 your_script >>/path2log/logfile  2>&1

In order to answer you...

That way I do not have any terminal output

Sorry when you say scheduler to me that means batchs... and so no terminals are attached... I understand better now... considered using tail -f /.../logfile ?

I guess I've found a solution using a wrapper :

Code:

#!/usr/bin/ksh

LADATE=$(date +'%Y%m%d_%H%M%S')
SCRIPT=$(basename $0)
REPRISE=${1:-debut}
FIN=${2:-fin}
PID=$$

CUR_DIR=/home/dpi/patrick/prj_mksysb
SERVER=$3

REPLOG=$CUR_DIR     # pour la phase de tests
REPLOGCTRL=$CUR_DIR #           "
LOG=${REPLOG}/${SCRIPT%.*}_${PID}_${LADATE}.log
LOGCTRL=${REPLOGCTRL}/${SCRIPT%.*}_${SERVER}.log

> ${LOG}
> ${LOGCTRL}

. ${CUR_DIR}/tstout.ksh $1 $2 $3 2>&1 | tee ${LOG}

exit

which calls tstout.ksh program :

Code:

#!/usr/bin/ksh

print $1" "$2" "$3

print aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
print bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
print cccccccccccccccccccccccccccccccccccccccccccccccccc

I launch it using : ./wrapper.ksh linux openbsd freebsd

And it works fine : it feeds my log files and terminal outputs are available for the scheduler. I tests it into the scheduler, it's OK too.

It's not completely clear in my mind, but job is done

Thanks for sharing... When I will have a bit more time I will look more deeply the code...