08-21-2007
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I did a search for this topic but I couldn't find it and I was sure I have seen something similar before (hard because I am not sure of the criteria for the keywords)
What I was looking for was to be able to echo a message to the screen from a bash.sh script at the same time logging it to a... (2 Replies)
Discussion started by: Shakey21
2 Replies
2. Shell Programming and Scripting
Hello all!..
does anyone know the syntax to print to the screen and to a file?
Im using something like
AWK ....
print header |tee -a invalid_csv_file ;
END {..}
' invalid_csv_file="$invalid_csv_dir_file"
but no joy?
I get sh:... (2 Replies)
Discussion started by: satnamx
2 Replies
3. Shell Programming and Scripting
I want to output screen messages to a logfile when executing an automated script. I have tried the script and command to do this but with no luck.
Thanks,
Nicole (5 Replies)
Discussion started by: nsutti
5 Replies
4. Shell Programming and Scripting
Hello,
I need to print messages both to screen and to file handle in perl , like tee does in unix .
Any suggestions ?
Thanks (2 Replies)
Discussion started by: Alalush
2 Replies
5. UNIX Desktop Questions & Answers
I would like to use a terminal session to ssh to switches and routers. I need to capture data while logged into switches to a file I can email for troubleshooting.
I use termial to log into Cisco switch, run the sh tech command, and then sent the output to cisco. Is there a way to run a... (4 Replies)
Discussion started by: tdelliott
4 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
I have a script that bulk loads thousands of lines of data. I need to log the output during the execution of the script.
I know I can redirect (">") the output to a file; however, I want the output going to both the screen and the log file.
I thought I could use pipe to pipe the... (10 Replies)
Discussion started by: orahi001
10 Replies
7. Shell Programming and Scripting
Is it possible to store all standard-out of a bash script and the binaries it calls in a log file AND still display the stdout on screen?
I know this is possible to store ALL stdout/stderr of a script to a single log file like:
exec 1>&${logFile}
exec 2>&1
But running a script with the... (3 Replies)
Discussion started by: ckmehta
3 Replies
8. Shell Programming and Scripting
Hi,
I would need to log the whole screen ouput to a log file.
All Inputs from the Agent, all echo´s and DBMS Outputs from the PL/SQL.
Basicly everything what I can see during the run on the screen.
I tried it already with
#exec 2>$BASELOG/RUN.log
#exec 1>$BASELOG/RUN.log
#exec >... (1 Reply)
Discussion started by: enjoy
1 Replies
9. Shell Programming and Scripting
How can i print the output of a perl script on a unix console and redirect the same in a log file under same directory simultaneously ?
Like in Shell script, we use tee, is there anything in Perl or any other option ? (2 Replies)
Discussion started by: butterfly20
2 Replies
10. Shell Programming and Scripting
c()
{
if something failed;then
echo "failed"
exit 1
fi
}
f()
{
functinona #if something failed call "c"
functionb #if something failed call "c"
}
f > log 2>&1 #put the log to file not print on the screen
I want all the stdout/stdrr to the log file... (3 Replies)
Discussion started by: yanglei_fage
3 Replies
LEARN ABOUT OPENDARWIN
nice
NICE(1) BSD General Commands Manual NICE(1)
NAME
nice -- execute a utility at an altered scheduling priority
SYNOPSIS
nice [-n increment] utility [argument ...]
DESCRIPTION
The nice utility runs utility at an altered scheduling priority, by incrementing its ``nice'' value by the specified increment, or a default
value of 10. The lower the nice value of a process, the higher its scheduling priority.
The superuser may specify a negative increment in order to run a utility with a higher scheduling priority.
Some shells may provide a builtin nice command which is similar or identical to this utility. Consult the builtin(1) manual page.
ENVIRONMENT
The PATH environment variable is used to locate the requested utility if the name contains no '/' characters.
EXAMPLES
Execute utility 'date' at priority 5 assuming the priority of the shell is 0:
nice -n 5 date
Execute utility 'date' at priority -19 assuming the priority of the shell is 0 and you are the super-user:
nice -n 16 nice -n -35 date
DIAGNOSTICS
If utility is invoked, the exit status of nice is the exit status of utility.
An exit status of 126 indicates utility was found, but could not be executed. An exit status of 127 indicates utility could not be found.
SEE ALSO
builtin(1), csh(1), idprio(1), rtprio(1), getpriority(2), setpriority(2), renice(8)
COMPATIBILITY
The traditional -increment option has been deprecated but is still supported.
STANDARDS
The nice utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
A nice utility appeared in Version 4 AT&T UNIX.
BSD
June 6, 1993 BSD