04-17-2009
Can STDERR be saved to a variable
Guys i'm trying to save STDERR to a variable for a portion of my ksh script on solaris.
I know i can create redirects to files as such:
exec 4>/tmp/lava
print "This will be saved to /tmp/lava and not screen"; >&4
print "This will be seen on screen" >&2
I want to save the STDOUT of a command to a variable and save STDERR to another without having to have files everywhere.
e.g tapelist=$( command blah blah )
I then want to check if tapelist contains anything and run stuff otherwise dont
i.e
if [[ -n "{tapelist}" ]];then
do stuff....
else
do other stuff
fi
If the command fails it produces STDERR output i want to save so i can print it out later.
So in my thoughts although i know this doesnt work :-
savestderr="";
exec 3>${savestderr}
tapelist=$(command blah blah 2>&3)
Then can reference the error message as ${savestderr} Any ideas?
Last edited by lavascript; 04-17-2009 at 08:38 AM..
Reason: whats wrong with the formatting?
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
I have edited my sudoers file. I am using visudo command
I have added the following lines and saved the file.
I am saving the lines as :wq
But I am very amazed to see that these lines are not written in the sudoers file. I have retried the above process many times, when I... (0 Replies)
Discussion started by: Asteroid
0 Replies
2. UNIX and Linux Applications
I have just tried out Bluefish as an alternative to my regular text editor. If I save the modified preferences and reboot, the preferences have to be reentered again. Does anyone know which file the preferences are saved in?
The command
find / -mmin -5 | grep bluefish
yields zero hits.
Thanks... (2 Replies)
Discussion started by: figaro
2 Replies
3. UNIX for Dummies Questions & Answers
ok, heres my problem.
i have saved the last line from a ls -l command into a variable. What i want to do is be able to cut the second character into that (i.e. the r if its there of the - if its not there) and save that value into another variable.
here is the current code i have to save... (1 Reply)
Discussion started by: strasner
1 Replies
4. UNIX for Dummies Questions & Answers
step 1
# alias
alias cp='cp -i'
alias l.='ls -d .* --color=tty'
alias ll='ls -l --color=tty'
alias ls='ls --color=tty'
alias mv='mv -i'
alias rm='rm -i'
alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
step 2
# cat ~/.bashrc
# .bashrc (3 Replies)
Discussion started by: cqlouis
3 Replies
5. Shell Programming and Scripting
in my perl script
i tried the below statement
$result = `cleartool rmstream -f $s1 1> /dev/null`;
so as to redirect then error messages,when i print the $result
,it seems to be Null. (4 Replies)
Discussion started by: ram_unx
4 Replies
6. UNIX for Dummies Questions & Answers
Hi ,
Script File Is Not Getting Saved This Are The Steps I Am Following For Saving And Executing A Script
1). vi ( To Open Vi Editor )
2). vi filename ( vi firstprog.ksh)
#!bin\kash
date
3) !wq :( Saving And Quit) When I Am Saving The Scrpit I Am Getting The Below... (1 Reply)
Discussion started by: anudeepkumar123
1 Replies
7. Solaris
Hi Guys,
After setting below paths:
ok nvalias rootdisk /pci@1c,600000/scsi@2/disk@0,0:a
ok nvalias rootmirror /pci@1c,600000/scsi@2/disk@1,0:a
ok nvstore
to check:
ok devalias
devailas does show set path but after reboot
The alias for disks are not getting saved.
I get this error:-... (5 Replies)
Discussion started by: manalisharmabe
5 Replies
8. Shell Programming and Scripting
Hello,
Can you please if the bellow is the proper way of appending a variable to the stderr:
The easiest way to test this,I was able to imagine, was by touching 5 files and afterwards looping trough to the results:
-rw-r--r-- 1 ab owner 0 Sep 14 13:45 file1
-rw-r--r-- 1 ab owner 0 Sep... (7 Replies)
Discussion started by: alex2005
7 Replies
9. Shell Programming and Scripting
This may be wrong place to ask.
I am currently modifying "stock" configuration file and making slow progress.
Run into a snag - twice so far.
I can work on the project switching from editing to run all day long, no issue.
Next day i cannot access the file to run it.
The file... (8 Replies)
Discussion started by: annacreek
8 Replies
exec(1) User Commands exec(1)
NAME
exec, eval, source - shell built-in functions to execute other commands
SYNOPSIS
sh
exec [argument...]
eval [argument...]
csh
exec command
eval argument...
source [-h] name
ksh
*exec [arg...]
*eval [arg...]
DESCRIPTION
sh
The exec command specified by the arguments is executed in place of this shell without creating a new process. Input/output arguments may
appear and, if no other arguments are given, cause the shell input/output to be modified.
The arguments to the eval built-in are read as input to the shell and the resulting command(s) executed.
csh
exec executes command in place of the current shell, which terminates.
eval reads its arguments as input to the shell and executes the resulting command(s). This is usually used to execute commands generated as
the result of command or variable substitution.
source reads commands from name. source commands may be nested, but if they are nested too deeply the shell may run out of file descrip-
tors. An error in a sourced file at any level terminates all nested source commands.
-h Place commands from the file name on the history list without executing them.
ksh
With the exec built-in, if arg is given, the command specified by the arguments is executed in place of this shell without creating a new
process. Input/output arguments may appear and affect the current process. If no arguments are given the effect of this command is to mod-
ify file descriptors as prescribed by the input/output redirection list. In this case, any file descriptor numbers greater than 2 that are
opened with this mechanism are closed when invoking another program.
The arguments to eval are read as input to the shell and the resulting command(s) executed.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
EXIT STATUS
For ksh:
If command is not found, the exit status is 127. If command is found, but is not an executable utility, the exit status is 126. If a redi-
rection error occurs, the shell exits with a value in the range 1-125. Otherwise, exec returns a zero exit status.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
csh(1), ksh(1), sh(1), attributes(5)
SunOS 5.10 17 Jul 2002 exec(1)