10-22-2011
I'm not familiar with 'nano,' so maybe it's an interface issue, but it sounds like you need to type 'q' to get less to stop.
You could try running less with the -E option which won't write the end, nor will it wait for you to acknowledge the end with a 'q,' but it does tend to return the tty back to the original state when it reaches the end of the file, rather than leaving the tail of the file on display, which might not let you see what you are looking for. You could always go old school and pipe it to more which is more likely to behave as you are expecting it to.
This User Gave Thanks to agama For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
All,
I am running one perl script from prompt and its running fine, but while putting it on cron gives below error,
DB-Library error:
Could not open interface file. (2 Replies)
Discussion started by: Deei
2 Replies
2. OS X (Apple)
What I want my script to do is to run a command in Terminal and close that same Terminal window when the process is complete.
Of course I could ad a delay of 6 seconds to complete the process, but it may not be enough every time.
To simplify my question, this is what I want to achieve.... (9 Replies)
Discussion started by: ShadowofLight
9 Replies
3. Shell Programming and Scripting
p { margin-bottom: 0.08in; } As you can already tell I am a newbie. I took a Microsoft VB2008 a few month back. Now I'm taking Linux + and this course requires me to write scripts. The script executes but, I can't figure out or have not found anything that I can make out on the internet that can... (4 Replies)
Discussion started by: SANA4SPA
4 Replies
4. Shell Programming and Scripting
Good afternoon!
I have a script in cron that runs every ten minutes. Normally it only takes a minute or so to complete. However there are times when the amount of data it is looking at is large, and it has taken 20 minutes.
So I want for it to look for the script before it starts.
I was... (8 Replies)
Discussion started by: brianjb
8 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
I am new to Unix...
Can you please let me know how we can check if a script is running or not on Solaris box? (4 Replies)
Discussion started by: Rahul466
4 Replies
6. Shell Programming and Scripting
Hi freinds,
I have tried running a script through cron ,it is a shell script which calls a oracle procedure , problem here is that there is function in sql code which makes a external C call , this function is failing when running manually but works when run manually.
I have trouble shooted... (6 Replies)
Discussion started by: Jcpratap
6 Replies
7. Shell Programming and Scripting
i have script A and script B, both scripts have to run in parallel, my requirement is script A create table temp1, post creating it will run fr 4 hrs , script B has to start 0nly after creation of table temp1 ( which is done by script A) , again script B will run for 5 hrs
if i run sequencially... (7 Replies)
Discussion started by: only4satish
7 Replies
8. Shell Programming and Scripting
Hello.
This is my situation.
script .anything
ls -l .
---How can I see the content of .anything using (i.e) cat .anything?
If not possible can someone suggest a sequence to simulate a console-recorder
to "observ" from a RUNNING script session?
Thanks
Paolo
Please use code tags... (3 Replies)
Discussion started by: paolfili
3 Replies
9. Shell Programming and Scripting
Hi,
I do have an R script named KO.R. Basically reads thousands of files, whose name has a pattern that differs at a portion of the file name, List.txt.
Row_file1_mile.txt
Row_file2_mile.txt
Row_file3_mile.txt
...
...
Row_file1000_mile.txt
Below is a portion of my Rscript that reads... (4 Replies)
Discussion started by: Kanja
4 Replies
10. UNIX for Beginners Questions & Answers
Hi,
Whenever i try to open a file in any editor like vi, vim and nano i get this help.txt showing up in split screen without any key being pressed. This continues to pop up even when i close the help.txt. This behavior happens only when i am connected via putty. Is there a fix to this issue?
... (1 Reply)
Discussion started by: sunil0391
1 Replies
LEARN ABOUT OPENDARWIN
tail
TAIL(1) BSD General Commands Manual TAIL(1)
NAME
tail -- display the last part of a file
SYNOPSIS
tail [-F | -f | -r] [-b number | -c number | -n number] [file ...]
DESCRIPTION
The tail utility displays the contents of file or, by default, its standard input, to the standard output.
The display begins at a byte, line or 512-byte block location in the input. Numbers having a leading plus (``+'') sign are relative to the
beginning of the input, for example, ``-c +2'' starts the display at the second byte of the input. Numbers having a leading minus (``-'')
sign or no explicit sign are relative to the end of the input, for example, ``-n 2'' displays the last two lines of the input. The default
starting location is ``-n 10'', or the last 10 lines of the input.
The options are as follows:
-b number
The location is number 512-byte blocks.
-c number
The location is number bytes.
-f The -f option causes tail to not stop when end of file is reached, but rather to wait for additional data to be appended to the
input. The -f option is ignored if the standard input is a pipe, but not if it is a FIFO.
-F The -F option implies the -f option, but tail will also check to see if the file being followed has been renamed or rotated. The
file is closed and reopened when tail detects that the filename being read from has a new inode number. The -F option is ignored if
reading from standard input rather than a file.
-n number
The location is number lines.
-r The -r option causes the input to be displayed in reverse order, by line. Additionally, this option changes the meaning of the -b,
-c and -n options. When the -r option is specified, these options specify the number of bytes, lines or 512-byte blocks to display,
instead of the bytes, lines or blocks from the beginning or end of the input from which to begin the display. The default for the -r
option is to display all of the input.
If more than a single file is specified, each file is preceded by a header consisting of the string ``==> XXX <=='' where ``XXX'' is the name
of the file.
DIAGNOSTICS
The tail utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
cat(1), head(1), sed(1)
STANDARDS
The tail utility is expected to be a superset of the IEEE Std 1003.2-1992 (``POSIX.2'') specification. In particular, the -F, -b and -r
options are extensions to that standard.
The historic command line syntax of tail is supported by this implementation. The only difference between this implementation and historic
versions of tail, once the command line syntax translation has been done, is that the -b, -c and -n options modify the -r option, i.e. ``-r
-c 4'' displays the last 4 characters of the last line of the input, while the historic tail (using the historic syntax ``-4cr'') would
ignore the -c option and display the last 4 lines of the input.
HISTORY
A tail command appeared in PWB UNIX.
BSD
June 6, 1993 BSD