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 DEBIAN
debclean
DEBCLEAN(1) General Commands Manual DEBCLEAN(1)
NAME
debclean - clean up a sourcecode tree
SYNOPSIS
debclean [options]
DESCRIPTION
debclean walks through the directory tree starting at the directory tree in which it was invoked, and executes debian/rules clean for each
Debian source directory encountered. These directories are recognised by containing a debian/changelog file for a package whose name
matches that of the directory. Name matching is described below.
Also, if the --cleandebs option is given, then in every directory containing a Debian source tree, all files named *.deb, *.changes and
*.build are removed. The .dsc, .diff.gz and the (.orig).tar.gz files are not touched so that the release can be reconstructed if neces-
sary, and the .upload files are left so that debchange functions correctly. The --nocleandebs option prevents this extra cleaning behav-
iour and the --cleandebs option forces it. The default is not to clean these files.
debclean uses debuild(1) to clean the source tree.
Directory name checking
In common with several other scripts in the devscripts package, debclean will walk through the directory tree searching for
debian/changelog files. As a safeguard against stray files causing potential problems, it will examine the name of the parent directory
once it finds a debian/changelog file, and check that the directory name corresponds to the package name. Precisely how it does this is
controlled by two configuration file variables DEVSCRIPTS_CHECK_DIRNAME_LEVEL and DEVSCRIPTS_CHECK_DIRNAME_REGEX, and their corresponding
command-line options --check-dirname-level and --check-dirname-regex.
DEVSCRIPTS_CHECK_DIRNAME_LEVEL can take the following values:
0 Never check the directory name.
1 Only check the directory name if we have had to change directory in our search for debian/changelog. This is the default behaviour.
2 Always check the directory name.
The directory name is checked by testing whether the current directory name (as determined by pwd(1)) matches the regex given by the con-
figuration file option DEVSCRIPTS_CHECK_DIRNAME_REGEX or by the command line option --check-dirname-regex regex. Here regex is a Perl
regex (see perlre(3perl)), which will be anchored at the beginning and the end. If regex contains a '/', then it must match the full
directory path. If not, then it must match the full directory name. If regex contains the string 'PACKAGE', this will be replaced by the
source package name, as determined from the changelog. The default value for the regex is: 'PACKAGE(-.+)?', thus matching directory names
such as PACKAGE and PACKAGE-version.
OPTIONS
--cleandebs
Also remove all .deb, .changes and .build files from the parent directory.
--nocleandebs
Do not remove the .deb, .changes and .build files from the parent directory; this is the default behaviour.
--check-dirname-level N
See the above section Directory name checking for an explanation of this option.
--check-dirname-regex regex
See the above section Directory name checking for an explanation of this option.
--no-conf, --noconf
Do not read any configuration files. This can only be used as the first option given on the command-line.
-d Do not run dpkg-checkbuilddeps to check build dependencies.
--help Display a help message and exit successfully.
--version
Display version and copyright information and exit successfully.
CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced in that order to set configuration variables. Command line
options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently
recognised variables are:
DEBCLEAN_CLEANDEBS
If this is set to yes, then it is the same as the --cleandebs command line parameter being used.
DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
See the above section Directory name checking for an explanation of these variables. Note that these are package-wide configuration
variables, and will therefore affect all devscripts scripts which check their value, as described in their respective manpages and
in devscripts.conf(5).
SEE ALSO
debuild(1) and devscripts.conf(5).
AUTHOR
Christoph Lameter <clameter@debian.org>; modifications by Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities DEBCLEAN(1)