There are differences between tail -F and tail -f.
tail -f will continue reading a file for as long as possible, but if that file is renamed underneath it, then tail won't know and you will be wondering why you don't see anymore log lines being output to your terminal.
tail -F checks to see that the file we opened is still in the same location as before, so if the file is renamed underneath us, and a new file is created in its place (think log rotation) then it will open that new file and continue outputting data to its standard out.
I wish there was a tail -f <wildchar> that follow even if new files are created that match. my systems timestamp their logs by hour, and more than once I've been confused as to why the app just "stopped" just to realize that it's five past.
I am on my phone now (and, while its heart is a Linux kernel, it doesn't have a terminal, bash or tail. Maybe if you don't expand the wildcard tail will detect new files.
tail -f will continue reading a file for as long as possible, but if that file is renamed underneath it, then tail won't know and you will be wondering why you don't see anymore log lines being output to your terminal.
tail -F checks to see that the file we opened is still in the same location as before, so if the file is renamed underneath us, and a new file is created in its place (think log rotation) then it will open that new file and continue outputting data to its standard out.