This command useful for observing log files I don't know much about this kind of thing, but it seems odd to expect it to hang Tail will then listen for changes to that file
Tailblazer's "Pining For Kim" Animation: New Trailer & Updates!
If you remove the file, and create a new one with the same name the filename will be the same but it's a different inode (and probably stored on a.
What i want is a normal way to quit, like q in top
I am just curious about the. Say i have a huge text file (>2gb) and i just want to cat the lines x to y (e.g From what i understand i can do this by piping head into tail or viceversa, i.e Generally speaking, if it is possible to limit (in this case to 1) the number of lines a command's output has available/visible.
I wouldn't mind other commands just looking for that kind of behavior. $ touch $(seq 300) now the last 200 I am just curious about the question,. Why would you expect this to hang instead of simply returning 4096 bytes and exiting
