04-27-2017
Quote:
Originally Posted by
jim mcnamara
Writing to stderr is dependent on the environment of the process doing the actual write() call. A child process may possibly have a different view of what the #2 file descriptor points to.
Thanks for the input. If the errors return, I guess I will have to look into it a bit more. I actually don't think I need any of the output to the terminal because I am specifying an output file in the call. I could probably just redirect everything to /dev/null.
LMHmedchem
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to suppress the output to the screen. I am appending to a file so do not need the output on the screen in the CLI environment.
eg.
cat $HOME/somefile >> $HOME/anotherfile
I am doing this a number of times with SQL output files so I can look at the finished file not on the screen in the... (3 Replies)
Discussion started by: jagannatha
3 Replies
2. UNIX for Dummies Questions & Answers
Hi ,
in the process of installing HBA's(IBM 6228's) for AIX 6F1 which was recently upgdared to 5.3 ML1
after the upgrade lppchk -v output displays the following.
>lppchk -v
lppchk: The following filesets need to be installed or corrected to bring
the system to a consistent state:
... (1 Reply)
Discussion started by: Student37
1 Replies
3. Shell Programming and Scripting
I am using this command
find . -type f -mmin "+$t" > holder
Unfortunatley that is also printing files that begin with a period. Such as .bash_history.
What can I do to supress files that begin with a period? (1 Reply)
Discussion started by: chrchcol
1 Replies
4. Shell Programming and Scripting
Hi
I have a shell script in which a string variable is saving following query.
SqlQuery="select a||'|'||b||'|'||c from dual"
I am trying to pass above query as a parameter to some script but its giving me error for "single quote". I tried suppressing it using \' instead of just ' but it... (1 Reply)
Discussion started by: mahabunta
1 Replies
5. UNIX for Advanced & Expert Users
Hi All
this is a simple script
#! /bin/bash
FileCnt=`ls -lrt $DIR/* | wc -l`
echo $FileCnt
how could i escape the error msg if there are no files in $DIR
ls: /home/sayantan/test/files/cnt/*: No such file or directory
0
Looking forward for a quick reply
Regards, Newbie (2 Replies)
Discussion started by: newbie07
2 Replies
6. Programming
I wanna remove element from xml file, when I run the following code I get the correct output when I'm outputing to console but when I'm trying to ouptup the same code to a file I get the same / original xml file without removed element, here is the code :
import java.io.*;
import... (3 Replies)
Discussion started by: c0mrade
3 Replies
7. Shell Programming and Scripting
Hi
I have a script which connects to oracle using sqlplus
if ! check_sqlplus "$ORACLE_SID" ; then
echo "Unable to use sqlplus for sid $ORACLE_SID"
return 1
else
echo "attempting to connect to database"
echo $ORACLE_HOME
echo $ORACLE_SID
echo "Status before entering... (2 Replies)
Discussion started by: xiamin
2 Replies
8. AIX
Hello AIX and Java gurus,
I have a java error that I have no clue how to resolve. I am trying to run the popular NMONVisualizer utility against a NMON dataset and getting the error as shown below:
/db2storage/NMON >java -jar NMONVisualizer_2015-02-02.jar com.ibm.nmon.ReportGenerator... (1 Reply)
Discussion started by: okonita
1 Replies
9. Shell Programming and Scripting
I have the below two commands in my script.
tar -xf hello.tar
unzip -o tempp.zip
When i run the script i see the below on my standard out.
How can i suppress output coming from both the tar and unzip on my standard output. (3 Replies)
Discussion started by: mohtashims
3 Replies
10. Shell Programming and Scripting
After a bash function is run the below file is produced:
out_name.txt tab-delimeted
Input Errors and warnings AccNo Genesymbol Variant Reference Sequence Start Descr. Coding DNA Descr. Protein Descr. GeneSymbol Coding DNA Descr. GeneSymbol Protein Descr. Genomic... (3 Replies)
Discussion started by: cmccabe
3 Replies
LEARN ABOUT OPENDARWIN
script
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-a] [-k] [-q] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command ... is given, script will run the specified command with an optional argument vector instead of an interactive shell.
Options:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-d (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variable is utilized by script:
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO
csh(1) (for the history mechanism).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD
June 6, 1993 BSD