Commands using tail (292)
-
-3mount |tail -1 | less -p "/dev/[^ ]*"
-
-3find . -type d -print0 | xargs -0 du -s | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {} | sort -rn
-
prints a random line
-4head -$(($RANDOM % $(wc -l < file.txt) +1 )) file.txt | tail -1 -
-4echo -e "HEAD / HTTP/1.1\nHost: slashdot.org\n\n" | nc slashdot.org 80 | head -n5 | tail -1 | cut -f2 -d-
-
-4echo -e "GET /automation/n09230945.asp HTTP/1.0\r\nHost: whatismyip.com\r\n" | nc whatismyip.com 80 | tail -n1
-
Takes a directory name as an argument (defaults to current directory if no arguments are given). Prints the newest file in the directory. Show Sample Output
-4lastfile () { find ${1:-.} -maxdepth 1 -type f -printf "%T+ %p\n" | sort -n | tail -n1 | sed 's/[^[:space:]]\+ //'; } -
(follow with next command) tail -f from.log | colorize.pl +l20:".*" & Use with http://www.commandlinefu.com/commands/view/10031/intercept-monitor-and-manipulate-a-tcp-connection. - can use to view output of tees that send traffic to files - output will be interwoven with red for sent traffic and green for received. get colorize.pl from http://www.flinkmann.de/71-1-Colorizepl.html
-4tail -f to.log | colorize.pl +l10:".*" & -
Watches for file modifications in the current directory and tails the file.
-4watch 'ls -tr1 | tail -n1 | xargs tail' -
-5tail -n +4 | head -n 1
-
this command shows the space used in postgres directory. Show Sample Output
-5while (( 1==1 )); do du -c . >> output.log; sleep 2; done; tail -f output.log -
Silly approach, but easy to remember... Show Sample Output
-5head -n 13 /etc/services | tail -n 1 -
Tail is much faster than sed, awk because it doesn't check for regular expressions. Show Sample Output
-5tail -n +<N> <file> | head -n 1 -
Debian-specific but very useful as cron files are prone to very subtle gotchas
-7/etc/init.d/cron restart && tail -100 /var/log/syslog -
tail -n X | head -n 1 prints a specific line, where X is the line number
-7tail -n 4 | head -n 1 -
I know how hard it is to find an old command running through all the files because you couldn't remember for your life what it was. Heres the solution!! Grep the history for it. depending on how old the command you can head or tail or if you wanted to search all because you cannot think how long ago it was then miss out the middle part of the command. This is a very easy and effective way to find that command you are looking for.
-9cat .bash_history | tail -100 | grep {command} -
-11/usr/bin/lynx -dump http://www.netins.net/dialup/tools/my_ip.shtml | grep -A2 "Your current IP Address is:" | tail -n1 | tr -d ' '|sed '/^$/d'| sed 's/^ *//g'
-
In cases when the user is following a log file that rotates then it is advisable to use the -F option as it keeps following the log even when it is recreated, renamed, or removed as part of log rotation. To interrupt tail while it is monitoring, break-in with Ctrl+C.
-12tail -f <file> - ‹ First < 10 11 12
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Check These Out
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
- » commands using tail