10-29-2007
avoid displaying errors while executing a script
Hi all,
I am running a script on bash shell, although it gives me the desired output, it displays some errors at the prompt like
this directory doesnt exists
unary operator
etc etc
Is there someway to avoid these errors ??
Its very annoying to have these errors while the script is executing.
Thanks
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I tried a simple hello.cc program in Unix.
- Compiled with no errors
- Created a.out successfully
- While executing a.out, following error message appeared
" ld.so.1:a.out fatal: libstdc++.so.2.10.0: Open failed: No such file or directory Killed"
... (1 Reply)
Discussion started by: nirthana
1 Replies
2. Programming
Problem background:
gcc v 4.1
2 .cpp files, 2 .h files
Files:
main.cpp
a.cpp
a.h
b.h
Organization:
main.cpp includes a.h (because it calls a.cpp code)
a.cpp includes a.h
a.h includes b.h (because a class in a.h uses a b.h class)
There is no inheritance between a.h or b.h or any of... (1 Reply)
Discussion started by: johnqsmith
1 Replies
3. Shell Programming and Scripting
Hi All,
I am using mysql at sun solaris unix(Hp) server. I logged into mysql server with root as user. its logged in properly. Then i used 'show databases' mysql command. its display all the available databases.
for example
mysql > show databases;
It displayed as follows.
exampledb1
... (1 Reply)
Discussion started by: dbsurf
1 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
I am using mysql at sun solaris unix(Hp) server. I logged into mysql server with root as user. its logged in properly. Then i used 'show databases' mysql command. its display all the available databases.
for example
mysql > show databases;
It displayed as follows.
exampledb1... (1 Reply)
Discussion started by: dbsurf
1 Replies
5. Solaris
Hello,
this is solaris 10 on SF v440,
I know below errors might go away if I put a new PS or put the original one back in socket but is there any other way to stop these errors from appearing in /var/adm/messages ? I do not want to put the failed PS1 in socket neither do we want to spend on... (5 Replies)
Discussion started by: upengan78
5 Replies
6. Shell Programming and Scripting
Hello , i am using RHEL5 , i have got a perl script that executes and sends an email correctly if i run it with ./sendemail.sh command. This is the script below
#! /usr/bin/perl
use Net::SMTP;
print "starting email send .";
$smtp = Net::SMTP->new("192.168.0.1");... (2 Replies)
Discussion started by: kabazzi
2 Replies
7. Shell Programming and Scripting
Sorry for my english!
I'm using Debian squeeze and for an assignement, i have create 2 virtual pdf cups printers. Both are working very well.
To test the different administion command; i try to disable one of the printer and move his queue file to the second one. I'm able to do it easily.
... (4 Replies)
Discussion started by: lyapma
4 Replies
8. Shell Programming and Scripting
I'm working on a script that will search through a directory for MKV files and remux them to MP4. I found a few other scripts around the net that do this, but they all have limitations that don't always get the job done. The main limitation I've found is that most scripts look for the video track... (2 Replies)
Discussion started by: rayne127
2 Replies
9. Shell Programming and Scripting
code:
IMAGE=$imgvalue;
if
then
echo DO=ABC;
elif
then echo DO=ETC;
elif
then echo DO=XYZ;
else
echo "$imgvalue is unsupported";
exit 1;
fi
in above script IMAGE=1 , IMAGE=2, IMAGE=3 whatever may be the value i have assigned it's showing only DO=ABC other conditions... (7 Replies)
Discussion started by: saku
7 Replies
10. AIX
I am building a bff using mkinstallp.
My template file is :
Package Name: svr_exForum
Package VRMF: 7.2
Update: N
Fileset
Fileset Name: svr_exForum.rte
Fileset VRMF: 7.2
USRLIBLPPFiles
Pre-installation Script: /lppdir/lpp/exForum/F_pre_i
... (2 Replies)
Discussion started by: kevinl
2 Replies
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-akq] [-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.
The following options are available:
-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
January 22, 2004 BSD