06-05-2009
-F or --retry doesn't seem to work on my system (AIX 5.3):
$>tail -n1 -F IMC_Stats.log
Usage: tail [-f] [-c Number|-n Number|-m Number|-b Number|-k Number] [File]
Usage: tail [-r] [-n Number] [File]
Usage: tail [+|-[Number]][l|b|c|k|m][f] [File]
$>tail -n1 --retry IMC_Stats.log
Usage: tail [-f] [-c Number|-n Number|-m Number|-b Number|-k Number] [File]
Usage: tail [-r] [-n Number] [File]
Usage: tail [+|-[Number]][l|b|c|k|m][f] [File]
Any other ideas are appreciated...
Quote:
Originally Posted by
mglenney
Disclaimer: I use bash, not ksh
use -F or --retry. So:
tail -n1 -f --retry /home/dirTalk/current_dir/oamlog/ASAI.log | while read output_line
or
tail -n1 -F /home/dirTalk/current_dir/oamlog/ASAI.log | while read output_line
MG
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there,
I have a problem here that involves bash script since I was noob in that field. Recently, I have to monitor data involve in logs so I just run command tail -f for the monitoring. The logs was generate every hour so I need to quickly change my logs every time the new hour hits according... (2 Replies)
Discussion started by: kriezo
2 Replies
2. AIX
Hi
Im looking to create a Aix script to monitor a file for once it's been updated and then send an email. I dont have great scripting knowledge and have only come up with the following so far
while true
do
find /home/test/AMQ* -mmin 1 > /home/test/scripts/output/MQERRORS
exec... (2 Replies)
Discussion started by: elmesy
2 Replies
3. Shell Programming and Scripting
hi All,
how to find a pattern in the log file & display the above and below line
for example in the log file, i have many lines, whenever i search for "Category" it should display the above line with only few parameter like i want only the location name & department name
Thu Jul 02 11:05:23... (2 Replies)
Discussion started by: rithick256
2 Replies
4. Shell Programming and Scripting
Trying to use code that I found to send only new lines out of a log file by doing:
while :; do
temp=$(tail -1 logfile.out)
awk "/$last/{p=1}p" logfile.out #pipe this to log analyzer program
last="$temp"
sleep 10
done
Script works fine when logfile is basic text, but when it contains... (2 Replies)
Discussion started by: moo72moo
2 Replies
5. Shell Programming and Scripting
Hi,
Have written a script to monitor linux non standard log file based on line numbers, so each check store $otalinenum ..
then in next check after 10 minutes it compre the current_total_line_num > last_total_line_num then it will parse the log file from last_total_line_num to... (0 Replies)
Discussion started by: Shirishlnx
0 Replies
6. Shell Programming and Scripting
Title: Use “tail -f” to monitor and report, but the top line should be always fixed on the screen.
Hi, dear Unix experts,
I am trying to find a Unix command (or scripting) on how to continuously display a text file of its last several lines of contents. But during this displaying, I want some... (2 Replies)
Discussion started by: df3c
2 Replies
7. Shell Programming and Scripting
Hi
I am looking for a help in designing a bash script on linux which can do below:-
1) Look in a specific directory for any new files
2) Mail the content of the new file
Appreciate any help
Regards
Neha (5 Replies)
Discussion started by: neha0785
5 Replies
8. Post Here to Contact Site Administrators and Moderators
Kindly advice with shell script to monitor open file in linux, if the open file count is greater then 5000 then send me an email..
command : lsof | wc -l (0 Replies)
Discussion started by: adminhelp
0 Replies
9. UNIX for Beginners Questions & Answers
Hello,
I would like to write script to tail a file for different environment
But the number of lines are keep changing
How can I write a script
For example:
env could : A, B or C
and log files could be a.log, b.log and c.log
with the number of lines can change
say sometimes it 100 last... (9 Replies)
Discussion started by: encrypt_decrypt
9 Replies
TAIL(1) FSF TAIL(1)
NAME
tail - output the last part of files
SYNOPSIS
tail [OPTION]... [FILE]...
DESCRIPTION
Print the last 10 lines of each FILE to standard output. With more than one FILE, precede each with a header giving the file name. With
no FILE, or when FILE is -, read standard input.
Mandatory arguments to long options are mandatory for short options too.
--retry
keep trying to open a file even if it is inaccessible when tail starts or if it becomes inaccessible later -- useful only with -f
-c, --bytes=N
output the last N bytes
-f, --follow[={name|descriptor}]
output appended data as the file grows; -f, --follow, and --follow=descriptor are equivalent
-F same as --follow=name --retry
-n, --lines=N
output the last N lines, instead of the last 10
--max-unchanged-stats=N
with --follow=name, reopen a FILE which has not changed size after N (default 5) iterations to see if it has been unlinked or
renamed (this is the usual case of rotated log files)
--pid=PID
with -f, terminate after process ID, PID dies
-q, --quiet, --silent
never output headers giving file names
-s, --sleep-interval=S
with -f, sleep for approximately S seconds (default 1.0) between iterations.
-v, --verbose
always output headers giving file names
--help display this help and exit
--version
output version information and exit
If the first character of N (the number of bytes or lines) is a `+', print beginning with the Nth item from the start of each file, other-
wise, print the last N items in the file. N may have a multiplier suffix: b for 512, k for 1024, m for 1048576 (1 Meg).
With --follow (-f), tail defaults to following the file descriptor, which means that even if a tail'ed file is renamed, tail will continue
to track its end. This default behavior is not desirable when you really want to track the actual name of the file, not the file descrip-
tor (e.g., log rotation). Use --follow=name in that case. That causes tail to track the named file by reopening it periodically to see if
it has been removed and recreated by some other program.
AUTHOR
Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, and Jim Meyering.
REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>.
COPYRIGHT
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
The full documentation for tail is maintained as a Texinfo manual. If the info and tail programs are properly installed at your site, the
command
info tail
should give you access to the complete manual.
tail (coreutils) 4.5.3 February 2003 TAIL(1)