Emergency UNIX and Linux Support

Please show what you tried and what happened. Obviously "script" must not be running if you want to capture the output using shell commands.

script command will open a new shell and only when u type exit can it end .. i m not sure u can use the command like that inside the script .. if capturing the output and error of the commands fired is ur goal then why dont u use 2>&1 .. that should suffice ur need .

use bactics.

generally when you write in a script, you use them.

i am not sure if it will work but you may try that out.

Hi.

I tried solution # 2 in post # 7. The kernel.org command script did not compile on aix (a few errors with header files as I recall), whereas it did compile without errors on GNU/Debian Linux.

I don't have access to an SCO box, so I used aix simply because it was different from Linux, as SCO is different from Linux. The result was not totally unexpected, and was a good exercise. I did not investigate farther ... cheers, drl

Hi,

Thanks for all your inputs. I tried lot of things inside the shell script to use this script ( I cannot install any extra utilities on the boxes) but still looking for a exit from the shell prompt. So we decided to use some other methods.

Thanks for all your help.

Regards,

Ravi

Depending on your operating system you should try both :

a) /sbin/initprivs 2>&1 >mylogfile

b) /sbin/initprivs >mylogfile 2>&1

For example, i guess in HP-UX, the first one put the error into the log file which is what you may expect, but if you use Solaris, this will fail since the error has been sent to file descriptor 1 before it has been told to redirect into the log file : in Solaris, you should then use the way b).

Or just ...

/sbin/initprivs >initprivs.log 2>initprivs.err

you could either use | tee logfile or |tee -a logfile (fork the display to the logfile, 'a' stand for append)

After 5 months I cannot relate the most recent post to the original post (which was about the unix "script" command.