Sponsored Content
Full Discussion: Validation in shell script.
Top Forums Shell Programming and Scripting Validation in shell script. Post 302470391 by Scrutinizer on Wednesday 10th of November 2010 03:16:46 AM
Old 11-10-2010
3. Check out inotifywait on Linux.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need help in file validation by shell script

Hi I am new to this forum.I need a help in the following: We receve pipe delimited file with transaction ID,tran_date,Quest_cd,Ans_cd,ans_value. Same transaction ID can be repeated with different quest_cd and ans_cd. Basically I need to check if a perticular pair of quest_cd and ans_cd... (1 Reply)
Discussion started by: srichakra
1 Replies

2. Shell Programming and Scripting

Test File Reading & Validation using Shell script

Please help develop script for below requirement -------Sample file------------------------------- HSVSHOSTRECON 20090115011817BP DARMAR60064966247003504720000000000000000000066626000000000000133000003D003463001332 ... (14 Replies)
Discussion started by: niraj_bhatt
14 Replies

3. Shell Programming and Scripting

shell script data & time validation

How to validate a date and optionly a time in shell scripting when i get the date and time as pararmeters that sent out with the call of the file? (in my case sh union.sh `first parameter ,second parameter...` (4 Replies)
Discussion started by: tal
4 Replies

4. Shell Programming and Scripting

EMail Address Validation (Shell Script)

Hi, Can anyone provide me the code snippet for EMail Address Validation. User is going to enter the email address in form window. I need to validate the format is correct. Thanks in Advance BS (3 Replies)
Discussion started by: balajiora
3 Replies

5. Shell Programming and Scripting

Shell script validation using process.

Hi All, I have a shell script in Linux and it will be invoked by 2 methods, 1) An automated background process . 2) Logining into the box and directly executing the script. I need to put a validation in my shell script such that it will be executed successfully on when an... (11 Replies)
Discussion started by: vininx
11 Replies

6. Shell Programming and Scripting

String validation in shell script

Hi All, I am a newbie...I would like to have a function which ll check if a file contains valid strings before "=" operator. Just to give you my requirement: assume my file has content: hello= gsdgsd sfdsg sgdsg sgdgdg world= gggg hhhh iiiii xxxx= pppp ppppp pppp my... (1 Reply)
Discussion started by: rtagarra
1 Replies

7. Shell Programming and Scripting

Help With UNIX Shell Scripting For Data Validation

Hi All, I am completely new to Unix Shell Scripting. I m validating(Basic File Validation) an .HHT file in TIBCO. After that i need to do Data Validation through UNIX Shell scripting. Rules in DataValidation: 1.) Need to Check Every field wheather it is a Char or Number?(Fields are... (1 Reply)
Discussion started by: Chaitanya K
1 Replies

8. Shell Programming and Scripting

Script for validation

Hi, I need a script which do below I have one process which runs 24*7 daily and I always has to monitor it now i want to have this automated such that if it stops at anytime we get a exception mail. For example i use ps -ef|grep 'etl' above command gives me the desired output. ... (7 Replies)
Discussion started by: sv0081493
7 Replies

9. UNIX for Dummies Questions & Answers

Validation to be added in the shell script

I need help with one of my shell script. The script is working fine but i need to add two condition - i need to get rid of all the below ftp messages and need to have only ftp completed or failed message. example when i run the script i get below lines - Connected to xxxx 220 (vsFTPd... (1 Reply)
Discussion started by: chandraprakash
1 Replies

10. Shell Programming and Scripting

Help with validation of URLs in shell script

hello every one I wrote the script to validate all the urls from my server . sourcing text file which contains the list of urls and trying to check every url and based on response printing url is up or not. the issue when i use the below code with url is printing url exist and and in loop it's... (3 Replies)
Discussion started by: markjohn1
3 Replies
inotifywait(1)						      General Commands Manual						    inotifywait(1)

NAME
inotifywait - wait for changes to files using inotify SYNOPSIS
inotifywait [-hcmrq] [-e <event> ] [-t <seconds> ] [--format <fmt> ] [--timefmt <fmt> ] <file> [ ... ] DESCRIPTION
inotifywait efficiently waits for changes to files using Linux's inotify(7) interface. It is suitable for waiting for changes to files from shell scripts. It can either exit once an event occurs, or continually execute and output events as they occur. OUTPUT
inotifywait will output diagnostic information on standard error and event information on standard output. The event output can be config- ured, but by default it consists of lines of the following form: watched_filename EVENT_NAMES event_filename watched_filename is the name of the file on which the event occurred. If the file is a directory, a trailing slash is output. EVENT_NAMES are the names of the inotify events which occurred, separated by commas. event_filename is output only when the event occurred on a directory, and in this case the name of the file within the directory which caused this event is output. By default, any special characters in filenames are not escaped in any way. This can make the output of inotifywait difficult to parse in awk scripts or similar. The --csv and --format options will be helpful in this case. OPTIONS
-h, --help Output some helpful usage information. @<file> When watching a directory tree recursively, exclude the specified file from being watched. The file must be specified with a rela- tive or absolute path according to whether a relative or absolute path is given for watched directories. If a specific path is explicitly both included and excluded, it will always be watched. Note: If you need to watch a directory or file whose name starts with @, give the absolute path. --fromfile <file> Read filenames to watch or exclude from a file, one filename per line. If filenames begin with @ they are excluded as described above. If <file> is `-', filenames are read from standard input. Use this option if you need to watch too many files to pass in as command line arguments. -m, --monitor Instead of exiting after receiving a single event, execute indefinitely. The default behaviour is to exit after the first event occurs. -d, --daemon Same as --monitor, except run in the background logging events to a file that must be specified by --outfile. Implies --syslog. -o, --outfile <file> Output events to <file> rather than stdout. -s, --syslog Output errors to syslog(3) system log module rather than stderr. -r, --recursive Watch all subdirectories of any directories passed as arguments. Watches will be set up recursively to an unlimited depth. Sym- bolic links are not traversed. Newly created subdirectories will also be watched. Warning: If you use this option while watching the root directory of a large tree, it may take quite a while until all inotify watches are established, and events will not be received in this time. Also, since one inotify watch will be established per subdi- rectory, it is possible that the maximum amount of inotify watches per user will be reached. The default maximum is 8192; it can be increased by writing to /proc/sys/fs/inotify/max_user_watches. -q, --quiet If specified once, the program will be less verbose. Specifically, it will not state when it has completed establishing all inotify watches. If specified twice, the program will output nothing at all, except in the case of fatal errors. --exclude <pattern> Do not process any events whose filename matches the specified POSIX extended regular expression, case sensitive. --excludei <pattern> Do not process any events whose filename matches the specified POSIX extended regular expression, case insensitive. -t <seconds>, --timeout <seconds> Exit if an appropriate event has not occurred within <seconds> seconds. If <seconds> is a negative value (the default), wait indefi- nitely for an event. -e <event>, --event <event> Listen for specific event(s) only. The events which can be listened for are listed in the EVENTS section. This option can be spec- ified more than once. If omitted, all events are listened for. -c, --csv Output in CSV (comma-separated values) format. This is useful when filenames may contain spaces, since in this case it is not safe to simply split the output at each space character. --timefmt <fmt> Set a time format string as accepted by strftime(3) for use with the `%T' conversion in the --format option. --format <fmt> Output in a user-specified format, using printf-like syntax. The event strings output are limited to around 4000 characters and will be truncated to this length. The following conversions are supported: %w This will be replaced with the name of the Watched file on which an event occurred. %f When an event occurs within a directory, this will be replaced with the name of the File which caused the event to occur. Other- wise, this will be replaced with an empty string. %e Replaced with the Event(s) which occurred, comma-separated. %Xe Replaced with the Event(s) which occurred, separated by whichever character is in the place of `X'. %T Replaced with the current Time in the format specified by the --timefmt option, which should be a format string suitable for passing to strftime(3). EXIT STATUS
0 The program executed successfully, and an event occurred which was being listened for. 1 An error occurred in execution of the program, or an event occurred which was not being listened for. The latter generally occurs if something happens which forcibly removes the inotify watch, such as a watched file being deleted or the filesystem containing a watched file being unmounted. 2 The -t option was used and an event did not occur in the specified interval of time. EVENTS
The following events are valid for use with the -e option: access A watched file or a file within a watched directory was read from. modify A watched file or a file within a watched directory was written to. attrib The metadata of a watched file or a file within a watched directory was modified. This includes timestamps, file permissions, extended attributes etc. close_write A watched file or a file within a watched directory was closed, after being opened in writeable mode. This does not necessarily imply the file was written to. close_nowrite A watched file or a file within a watched directory was closed, after being opened in read-only mode. close A watched file or a file within a watched directory was closed, regardless of how it was opened. Note that this is actually imple- mented simply by listening for both close_write and close_nowrite, hence all close events received will be output as one of these, not CLOSE. open A watched file or a file within a watched directory was opened. moved_to A file or directory was moved into a watched directory. This event occurs even if the file is simply moved from and to the same directory. moved_from A file or directory was moved from a watched directory. This event occurs even if the file is simply moved from and to the same directory. move A file or directory was moved from or to a watched directory. Note that this is actually implemented simply by listening for both moved_to and moved_from, hence all close events received will be output as one or both of these, not MOVE. move_self A watched file or directory was moved. After this event, the file or directory is no longer being watched. create A file or directory was created within a watched directory. delete A file or directory within a watched directory was deleted. delete_self A watched file or directory was deleted. After this event the file or directory is no longer being watched. Note that this event can occur even if it is not explicitly being listened for. unmount The filesystem on which a watched file or directory resides was unmounted. After this event the file or directory is no longer being watched. Note that this event can occur even if it is not explicitly being listened to. EXAMPLES
Example 1 Running inotifywait at the command-line to wait for any file in the `test' directory to be accessed. After running inotifywait, `cat test/foo' is run in a separate console. % inotifywait test Setting up watches. Watches established. test/ ACCESS foo Example 2 A short shell script to efficiently wait for httpd-related log messages and do something appropriate. #!/bin/sh while inotifywait -e modify /var/log/messages; do if tail -n1 /var/log/messages | grep httpd; then kdialog --msgbox "Apache needs love!" fi done Example 3 A custom output format is used to watch `~/test'. Meanwhile, someone runs `touch ~/test/badfile; touch ~/test/goodfile; rm ~/test/badfile' in another console. % inotifywait -m -r --format '%:e %f' ~/test Setting up watches. Beware: since -r was given, this may take a while! Watches established. CREATE badfile OPEN badfile ATTRIB badfile CLOSE_WRITE:CLOSE badfile CREATE goodfile OPEN goodfile ATTRIB goodfile CLOSE_WRITE:CLOSE goodfile DELETE badfile BUGS
There are race conditions in the recursive directory watching code which can cause events to be missed if they occur in a directory immedi- ately after that directory is created. This is probably not fixable. It is assumed the inotify event queue will never overflow. AUTHORS
inotifywait is written and maintained by Rohan McGovern <rohan@mcgovern.id.au>. inotifywait is part of inotify-tools. The inotify-tools website is located at: http://inotify-tools.sourceforge.net/ SEE ALSO
inotifywatch(1), strftime(3), inotify(7) inotifywait 3.20.1 August 05, 2019 inotifywait(1)
All times are GMT -4. The time now is 10:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy