03-14-2008
hi vinayrao,
i guess what this person intended was to filter a log file for error messages.
To do this propperly you need to learn regular expressions (see google).
0. make a copy of a logfile you can use as example
1. take a look at the file (using less,more) to find a common pattern for error messages
2. construct a filter for that pattern
lets assume that all error messages start with ERROR.
that you can use the cmd 'grep' to filter for lines starting with ERROR (grep "^ERROR" logfile)
now you need to get some order in the resulting output. you may need to sort it (see: sort) and remove
double lines (see: uniq) or to cut certain fields (see: cut).
If your UNIX box is propper installed you
may take a look into the man pages for these commands. iff you have the gnu coreutils
you can also get a lot of help from 'info coreutils' (note: first read how to use the info reader).
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Could someone please advise on a good way to implement error checking in a script?
i am taking input from a file, iserting it's values into two commands and sending the output of each to seperate log files. i need to check those log files for for an occurance of 'error', stop the command if... (3 Replies)
Discussion started by: gubten
3 Replies
2. Shell Programming and Scripting
Here is my problem
I'm designing a script that will have to accept user input from the command line using the read command.
The problem is that I have to check the input which should be in the format of
<first name> <last name> <phone number (8 digits long)>
The input can also be
... (4 Replies)
Discussion started by: pokeycam
4 Replies
3. Shell Programming and Scripting
I'm trying to create a directory from my Perl script. Only if the there was an error I want to let the user know about it. So if the folder exists is ok.
This is what I think should work:
`mkdir log 2>/dev/null`;
if($? == 0 || $? == errorCodeForFileExists)
{ everyting is fine }
else
{... (3 Replies)
Discussion started by: jepombar
3 Replies
4. Shell Programming and Scripting
I am creating a script that will automatically use sftp to connect to a site and download a file, extract the tar and then delete the tar file once completed.
What I am stuck on is the error checking for this process.
Here is the code so far:
Now this works for me as is, but i need... (0 Replies)
Discussion started by: xianoth
0 Replies
5. Shell Programming and Scripting
I am not very good with perl but trying to force myself to start learning...
I have a script that calls three other scripts in variables. I want to use a if statement to check the exit status and not sure how to do it..
This is basically what I have, the individual scripts print either a Y or... (1 Reply)
Discussion started by: i9300
1 Replies
6. Shell Programming and Scripting
What i need to do is when the database connection is not successful , the script should move to next list i.e skip the current.
But when i do this -
if ; then
break;
fi
The script break but it goes to the condition -
if ; then
for LIST in $LISTS
do
for TABLE in $TABLES
do... (2 Replies)
Discussion started by: dinjo_jo
2 Replies
7. Shell Programming and Scripting
Hi all,
I have following code:
export USERID=user
export BATCHHOSTIP=190.113.3.324
remotePath=/home/user
fileName=redbook.txt
EXIST=`ssh $USERID@$BATCHHOSTIP 'if ; then echo 0; else echo 1 ; fi'`
echo $EXIST
II run the code from other server. The redbook.txt file is exist in... (1 Reply)
Discussion started by: suigion
1 Replies
8. Programming
Hey guys i am facing a problem in my sql statement. I am trying to check if there is such a value in the database.
Code:
string NewMovie = "ww";
string queryText ;
queryText = "Select * from movie_info WHERE movie_title = '"+ NewTitle +"'";
... (1 Reply)
Discussion started by: gregarion
1 Replies
9. Shell Programming and Scripting
I am currently wrapping up a assignment for one of my classes. I need help writing some error checking logic. The problems I am having are:
keeping track of the records I have deleted and reported it back using echo.
I have no idea how to do this.
ensuring that line numbers fall... (1 Reply)
Discussion started by: Boltftw
1 Replies
10. Shell Programming and Scripting
HI All,
Whenever I write a shell script I always check if a command got executed successfully, even for the commands like cd, mv, rm and others, and even for the cases when there is ALMOST nothing to stop this commands from executing with success. so I am wondering if it is an overkill. I am... (1 Reply)
Discussion started by: rdogadin
1 Replies
LEARN ABOUT XFREE86
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)
NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS
--help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO
lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities CHECKBASHISMS(1)