Sponsored Content
Full Discussion: error checking in bash
Top Forums Shell Programming and Scripting error checking in bash Post 302075730 by tmarikle on Tuesday 6th of June 2006 12:16:44 PM
Old 06-06-2006
Many commands and scripts return an exit code of non zero if an error occurred. This would be a good place to start checking but what you are attempting with grep is common when log files are the only means for communicating error messages.

Code:
mkdir $2 2> yourlog
if [[ $? -ne 0 ]]
then
    start looking for errors in yourlog
fi

This redirect stderr to yourlog and if the exit code from "mkdir" is non zero, the log is checked. You can also capture the error message into arrays or variables whatever you prefer. I prefer arrays.
Code:
set -A ERROR_ARRAY $(mkdir $2 2>&1)
for i in ${ERROR_ARRAY[@]}
do
    ...
done

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need help with error checking

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

2. Shell Programming and Scripting

bash if loop for checking multiple parameters

Hello, I've got next problem: I want to examine at the beginning of a script in an if loop that: 1. Is there 4 parameters given 2. If first state is true then: is there switches -e and -d? 3. At the end, how can i indentify them as variebles regardlees to its order. I was thinking like... (2 Replies)
Discussion started by: szittyafergeteg
2 Replies

3. Programming

Error Checking

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

4. Shell Programming and Scripting

bash: checking file size -solved

Hello I have srv RHEL5, file system UTDM (EMC DiskXtender Unix/Linux File System Manager 3.5 & EMC Centera). it all works under the scheme: have disk is formatted with a file system UTDM, drive open network - NFS, it write data, then migrate the data in the repository - EMC Centera. There are... (0 Replies)
Discussion started by: moskovets
0 Replies

5. Shell Programming and Scripting

Error checking help.

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

6. Shell Programming and Scripting

Multiple condition checking in bash

Hi All, I am trying to check if two variables have value assigned to it. i am doing it like if ] then echo "Please specify either single hostname or host file for the report" usage exit fi But its not working for it.Even i specify values for both variables it dont go... (6 Replies)
Discussion started by: kailash19
6 Replies

7. Homework & Coursework Questions

bash error checking problems[solved]

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: I am trying to make a script called showtime that displays the current time for a given city. The problem is on... (6 Replies)
Discussion started by: kevin298
6 Replies

8. Shell Programming and Scripting

checking first argument for tag in bash script

I have a bash script where I pass an argument ./chris.bash "\argv Test" I want to detect if the user supplied \argv at the start of the argument (3 Replies)
Discussion started by: kristinu
3 Replies

9. Shell Programming and Scripting

Bash for checking and copy Daily files and send an email

Hello, Trying to get a bash for files received on daily basis and want to copy those files to different directory and send an email notification if file exists then send the file counts else Alert with no file received. FileName format: DailyTransaction_2015-03-09_ 200.csv before 200 their is... (1 Reply)
Discussion started by: krux_rap
1 Replies

10. Shell Programming and Scripting

Bash : Checking Large file for specific lines

Morning .. I have a file with approximately 1000 lines. I want to check that the file contains, for example, 100 lines. Something like whats given below is ugly. And even if I create a function I have to call it 100 times. I may need to look through multiple files at times. Is there a... (4 Replies)
Discussion started by: sumguy
4 Replies
MU(1)                                                         General Commands Manual                                                        MU(1)

NAME
mu - a set of tools to deal with Maildirs and message files, in particular to index and search e-mail messages. SYNOPSIS
mu [options] mu index [options] mu find [options] <search expression> mu view <file> [<files>] mu mkdir [options] <dir> [<dirs>] mu extract [options] <file> [<parts>] [<regexp>] mu cfind [options] [<regexp>] DESCRIPTION
mu is a set of tools for dealing with Maildirs and the e-mail messages in them. mus main function is to enable searching of e-mail messages. It does so by periodically scanning a Maildir directory tree and analyzing the e-mail messages found ('indexing'). The results of this analysis are stored in a database, which can then be queried. In addition to indexing and searching, mu also offers functionality for viewing messages, extracting attachments and creating maildirs, and searching and exporting contact information. mu can be used from the command line or can be integrated with various e-mail clients. This manpage gives a general overview of the available commands (index, find, etc.); each of the mu commands has its own man-page as well. COMMANDS
mu offers the following commands: index for indexing (analyzing) the contents of your Maildirs, and storing the information in a database. See mu-index(1) find for finding messages in your database, using certain search parameters. See mu-find(1) cfind for finding contacts (names + e-mail addresses) matching a certain expression, and exporting the results in various formats for use in other programs. mu-cfind(1) view for displaying e-mail messages. See mu-view(1) mkdir for creating Maildirs. See mu-mkdir(1) extract for extract MIME-parts (such as attachments) from messages. See mu-extract(1) COLORS
Some mu sub-commands support colorized output. If you don't want this, you can use the --nocolor/ option to disable it. Even then, colors will only shown when output goes to a sufficiently capable terminal (this roughly mirrors the --color=auto of the GNU-version of the ls- command). Instead of the --color/, you can also set the MU_NOCOLOR environment variable to non-empty to disable colors. Currently, mu find, mu view, mu cfind and mu extract support colors. ENCODING
mu's output is in the current locale, with the exceptions of the output specifically meant for output to UTF8-encoded files. In practice, this means that the output of commands index, view, extract is always encoded according to the current locale. The same is true for find and cfind, with some exceptions, where the output is always UTF-8, regardless of the locale. For cfind the exception is --format=bbdb. This is hard-coded to UTF-8, and as such specified in the output-file, so emacs/bbdb can handle it correctly without guessing. For find the output is encoded according the locale for --format=plain (the default), and UTF-8 for all other formats (json, sexp, xml). DATABASE AND FILE
Commands mu index and find and cfind work with the database, while the other ones work on invidual mail files. Hence, running iew, mkdir and extract does not require the mu database. The various commands are discussed in more detail in their own separate man-pages; here the general options are discussed. OPTIONS
mu offers a number of general options that apply to all commands, including mu without any command. --muhome causes mu to use an alternative directory to store and read its database and logs. By default, ~/.mu is used. -d, --debug makes mu generate extra debug information, useful for debugging the program itself. By default, debug information goes to the log file, ~/.mu/mu.log. It can safely be deleted when mu is not running. When running with --debug option, the log file can grow rather quickly. See the note on logging below. -q, --quiet causes mu not to output informational messages and progress information to standard output, but only to the log file. Error messages will still be sent to standard error. Note that mu index is much faster with --quiet, so it is recommended you use this option when using mu from scripts etc. --log-stderr causes mu to not output log messages to standard error, in addition to sending them to the log file. -v, --version prints mu version and copyright information. -h, --help lists the various command line options, while --help-index, --help-find and --help-all list only the options for respectively the specified command or for all commands. ERROR CODES
The various mu subcommands typically exit with 0 (zero) upon success, and non-zero when some error occured. The table lists the various error codes. exit code | error ----------+------------------------------------------- 1 | MU_ERROR 2 | MU_ERROR_IN_PARAMETERS 3 | MU_ERROR_INTERNAL 4 | MU_ERROR_NO_MATCHES | 11 | MU_ERROR_XAPIAN | 13 | MU_ERROR_XAPIAN_QUERY 14 | MU_ERROR_XAPIAN_DIR_NOT_ACCESSIBLE 15 | MU_ERROR_XAPIAN_NOT_UP_TO_DATE 16 | MU_ERROR_XAPIAN_MISSING_DATA 17 | MU_ERROR_XAPIAN_CORRUPTION 18 | MU_ERROR_XAPIAN_CANNOT_GET_WRITELOCK 30 | MU_ERROR_GMIME | 50 | MU_ERROR_CONTACTS 51 | MU_ERROR_CONTACTS_CANNOT_RETRIEVE | 70 | MU_ERROR_FILE 71 | MU_ERROR_FILE_INVALID_NAME 72 | MU_ERROR_FILE_CANNOT_LINK 73 | MU_ERROR_FILE_CANNOT_OPEN 74 | MU_ERROR_FILE_CANNOT_READ 75 | MU_ERROR_FILE_CANNOT_CREATE 76 | MU_ERROR_FILE_CANNOT_MKDIR 77 | MU_ERROR_FILE_STAT_FAILED 78 | MU_ERROR_FILE_READDIR_FAILED 79 | MU_ERROR_FILE_INVALID_SOURCE BUGS
Please report bugs if you find them: http://code.google.com/p/mu0/issues/list AUTHOR
Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> SEE ALSO
mu-index(1) mu-find(1) mu-cfind(1) mu-mkdir(1) mu-view(1) mu-extract(1) mu-easy(1) mu-bookmarks(5) User Manuals January 2012 MU(1)
All times are GMT -4. The time now is 10:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy