ksh

I'm looking for a solution (similar to the bash code below) to copy both stdout and stderr to a file in addition to the screen within ksh on Solaris. The following code works great in the bash shell: #!/usr/bin/bash # Clear the logfile >logfile.txt # Redirect all script output to a logfile as well as their normal locations exec > >(tee -a logfile.txt) exec 2> >(tee -a logfile.txt >&2) date ls -l /non-existent/path For some reason this is throwing a syntax error on Solaris. I assume it's because I can't do process substitution, and I've seen some posts suggesting the use of mkfifo , but I've

I want my ksh script to have different behaviors depending on whether there is something incoming through stdin or not: (1) cat file.txt | ./script.ksh (then do "cat <&0 >./tmp.dat" and process tmp.dat) vs. (2) ./script.ksh (then process $1 which must be a readable regular file) Checking for stdin to see if it is a terminal[ -t 0 ] is not helpful, because my script is called from an other script. Doing "cat <&0 >./tmp.dat" to check tmp.dat's size hangs up waiting for an EOF from stdin if stdin is "empty" (2nd case). How to just check if stdin is "empty" or not?! vladr EDIT: You are running on

I would like to create a pipe in a ksh script (using exec) that pipe's to a tee, and sends the output to a pipe. Current: #Redirect EVERYTHING exec 3>&1 #Save STDOUT as 3 exec 4>&2 #Save STDERR as 4 exec 1>${Log} #Redirect STDOUT to a log exec 2>&1 #Redirect STDERR to STDOUT What'd I'd like to do (but I don't have the syntax correct): #Redirect EVERYTHING exec 3>&1 #Save STDOUT as 3 exec 4>&2 #Save STDERR as 4 exec 1>tee -a ${Log} >&3 #Redirect STDOUT to a log exec 2>&1 #Redirect STDERR to STDOUT How can I create this pipe? Here's a solution I use. It works under ksh on my Mac. It's nicely

I've recently had to dust off my Perl and shell script skills to help out some colleagues. The colleagues in question have been tasked with providing some reports from an internal application with a large Oracle database backend, and they simply don't have the skills to do this. While some might question whether I have those skills either (grin), apparently enough people think I do to mean I can't weasel out of it. So to my question - in order to extract the reports from the database, my script is obviously having to connect and run queries. I haven't thus far managed to come up with a good