News for hackers. Stuff that matters.
Re:Stop using tail -f (mostly) by alayne on Saturday June 06, 2015 @04:39PM (#9672181)
Re:Stop using tail -f (mostly) by hansjorg on Saturday June 06, 2015 @04:33PM (#9672159)
Tried this for a while the last time I saw this posted somewhere, but went back to using tail.

Using less +F you're not able to add blank lines to the terminal. Seems kind of silly, but it's very useful to see if there has been any output since last time you took a look.

Re:Stop using tail -f (mostly) by borkabrak on Saturday June 06, 2015 @04:50PM (#9672217)
This is exactly the reason I've never switched to using `less +F`, as well. When I tail a log, I'm usually looking for sections of it corresponding to particular test runs. Adding blank lines or even rows of dashes/equal signs lets me make the distinction clearly visible.
Re:Stop using tail -f (mostly) by ajbetteridge on Sunday June 07, 2015 @03:53AM (#9673791)
Same here. I'm normally using "tail -f | grep something" which less +f doesn't seem to handle.
Re:Stop using tail -f (mostly) by ayanamist on Saturday June 06, 2015 @11:22PM (#9673282)
If file is very large like several gigabytes, `tail` is much faster than `less`
Re:Stop using tail -f (mostly) by DArcMattr on Sunday June 07, 2015 @03:06AM (#9673704)
I'm still going to use tail -f, in tmux. I get the log stream, and I get tmux's search & movement.