I tried to use in a bash script, the unix command script (to log all input/ouput from the shell)

#!/bin/bash

script toto.txt
ls
exit

The script command is executed but nothing happend after unless 'exit' is typed to stop the script command then ls is executed.

The unix command script seems to open a second bash shell (pts/2) where I guess the ls command has to be executed but I didn't have found a way to do it???

Any help would be great

Thierry

You can hit control and d key at the same time to stop the script command. Is that what you are asking?

No.

Better explanation, from the shell when the following is done:

%script toto.txt
Script started,.....
%ls
file1.txt file2.txt
%exit
Script ended
%more toto.txt
ls
file1.txt file2.txt
exit
%

toto.txt contains the ls command and the result printout

When I want to script that to get the same result

#!/bin/bash
script toto.txt
ls
exit

I have to do ctrl-d to stop the script command then ls is executed and toto.txt is empty.

If the only thing you need "toto.txt" to contain is the output from the "ls" command, then you could just pipe the output from "ls" to a file.
Else you could tell us why you need the "ls" command line to be there as well.

I used ls as an example in fact I am writing a script to perform regression testing of software build that happend each week.

Instead of running all the test by hand I wrote a script (that call each test case around 20) and I want to log what happend to be able to verify if any test failed (each testcase execution takes around 5 mn).

The script looks more like this:

script toto.txt
testcase1
testcase2
testcase3
......
testcase20
exit

Each testcase command gave on the shell a result printout (failed or passed)

I have found also that I could use the tee command like:

source mybashscript | tee toto.txt

but it would be more elegant to use the script command instead.

If it could not work too bad I will stick with tee!!!!

I just don't think using "script" is the right way, it's sposed to be an interactive tool. Why not "set -x" and pipe the output to a log, verify a test failed using exit status and on that basis parse logs?
Ridiculous example (but that's my approach):
logf="${__tmpdir}/$1.log"
parseLog() { grep "${logf}" <something>; do somethingElse; }
parseExit() { case $1 in 0) printf "%sOK\n";;
*) printf "%sFAILED\n"; parseLog;; esac; }
activate() { printf "%sActivating $1 "; set -x; $1 2>&1 "${logf}";
parseExit $?; set +x; }
for i in $(seq 0 2); do activate testcase${i}; done
# testcase? need to be functions within this script or sourced

Hope you get my point.

I got your point and I will look at the example that you gave.

I have to admit that it is a bit advance to me, I have started to do bash scripting monday. But I understand the concept!!

I didn't think to make the script to verify automaticaly the result of each testcases but this is a good idea.

Thanks for your help

Just pipe the commands to script:

echo "ls" | script toto.txt

for longer bits I'd suggest something like:

script toto.txt << EOF
ls
df
du
EOF

but it doesn't seem to work as expected. Anyway, hopefully this will help a little.