tail -f for live log monitoring in Linux CLI - Commands & Configuration

Introduction

Sometimes you want to watch a file as it changes in real time, like when checking logs to see what is happening right now. The tail -f command lets you do this by showing the end of a file and updating the display as new lines are added.

When you want to see new error messages as they appear in a server log file.

When you are debugging a program and want to watch its output live.

When monitoring access logs to track user activity on a website in real time.

When you want to follow the progress of a long-running script or process by watching its log.

When you need to confirm that a service is starting correctly by watching its startup logs.

Commands

This command shows the last 10 lines of the syslog file and keeps the terminal open to display new lines as they are added. It helps you watch system messages live.

Terminal

tail -f /var/log/syslog

Expected Output

Apr 27 10:00:01 server CRON[1234]: (root) CMD (run-parts /etc/cron.hourly)

Apr 27 10:00:02 server systemd[1]: Started Daily apt download activities.

Apr 27 10:01:15 server kernel: [12345.678901] usb 1-1: new high-speed USB device number 4 using xhci_hcd

→

-f - Follow the file as it grows, showing new lines in real time.

This command shows the last 20 lines of the syslog file and then follows it live. The -n 20 flag changes how many lines you see at the start.

Terminal

tail -n 20 -f /var/log/syslog

Expected Output

Apr 27 09:59:50 server systemd[1]: Starting Daily apt download activities...

Apr 27 10:00:01 server CRON[1234]: (root) CMD (run-parts /etc/cron.hourly)

Apr 27 10:00:02 server systemd[1]: Started Daily apt download activities.

Apr 27 10:01:15 server kernel: [12345.678901] usb 1-1: new high-speed USB device number 4 using xhci_hcd

→

-n - Show a specific number of lines from the end of the file before following.

→

-f - Follow the file as it grows.

This command stops the tail -f process by killing it. Use this to exit live monitoring when you are done.

Terminal

pkill -f 'tail -f /var/log/syslog'

Expected Output

No output (command runs silently)

→

-f - Match the full command line when searching for the process to kill.

Key Concept

If you remember nothing else from this pattern, remember: tail -f lets you watch a file live as it grows, showing new lines immediately.

Common Mistakes

Running tail without -f when wanting live updates

Without -f, tail only shows the last lines once and then exits, so you miss new lines added later.

Always add the -f flag to keep tail running and showing new lines as they appear.

Not stopping tail -f properly and closing the terminal abruptly

This can leave processes running in the background or cause confusion.

Use Ctrl+C to stop tail -f cleanly or kill the process with pkill if needed.

Summary

Use tail -f filename to watch the end of a file live as it grows.

Add -n number to show more lines at the start before following.

Stop live monitoring with Ctrl+C or by killing the tail process.

Practice

1. What does the command tail -f /var/log/syslog do?

easy

A. Copies the syslog file to another location

B. Deletes the syslog file permanently

C. Shows the last lines of the syslog file and updates live as new lines are added

D. Shows the first lines of the syslog file only once

Solution

1. Step 1: Understand the tail command

   The tail command shows the last part of a file.

2. Step 2: Understand the -f option

   The -f option makes tail keep running and show new lines as they are added to the file.

3. Final Answer:

   Shows the last lines of the syslog file and updates live as new lines are added -> Option C

4. Quick Check:

   tail -f = live log monitoring [OK]

Hint: Remember: -f means follow new lines live [OK]

Common Mistakes:

• Thinking tail -f deletes or copies files
• Confusing tail with head
• Expecting tail -f to show the start of the file

2. Which of the following is the correct syntax to continuously monitor the file /var/log/auth.log using tail?

easy

A. tail -n /var/log/auth.log

B. tail /var/log/auth.log -f

C. tail -follow /var/log/auth.log

D. tail -f /var/log/auth.log

Solution

1. Step 1: Identify correct option placement

   The option -f must come immediately after tail before the filename.

2. Step 2: Verify option correctness

   -f is the correct option to follow the file live; -follow is invalid and -n requires a number.

3. Final Answer:

   tail -f /var/log/auth.log -> Option D

4. Quick Check:

   Correct syntax = tail -f /var/log/auth.log [OK]

Hint: Options come before filename; -f not -follow [OK]

Common Mistakes:

• Placing options after filename
• Using invalid option -follow
• Using -n without a number

3. You run tail -f /var/log/app.log and see the following output after new log entries are added:

ERROR: Connection failed
INFO: Retrying connection
SUCCESS: Connected

What does this output indicate?

medium

A. The application is logging connection attempts and success live

B. The log file is empty and no new entries are added

C. The command failed to read the log file

D. The log file is being deleted while monitoring

Solution

1. Step 1: Understand tail -f output

   The command shows new lines added live to the log file.

2. Step 2: Interpret the log messages

   The messages show connection failure, retry, and success, indicating live logging of connection status.

3. Final Answer:

   The application is logging connection attempts and success live -> Option A

4. Quick Check:

   Live log updates = The application is logging connection attempts and success live [OK]

Hint: New lines mean live updates from the app log [OK]

Common Mistakes:

• Thinking the log file is empty
• Assuming command failed without error message
• Confusing deletion with normal log updates

4. You try to run tail -f /var/log/app.log but get the error: tail: cannot open '/var/log/app.log' for reading: Permission denied. What should you do to fix this?

medium

A. Delete the log file and try again

B. Run the command with sudo to get permission

C. Use head -f instead

D. Restart the system to fix permissions

Solution

1. Step 1: Understand the error message

   The error says permission denied, meaning the current user cannot read the file.

2. Step 2: Fix permission issue

   Running the command with sudo gives temporary admin rights to read the file.

3. Final Answer:

   Run the command with sudo to get permission -> Option B

4. Quick Check:

   Permission denied fix = use sudo [OK]

Hint: Permission denied? Try sudo before the command [OK]

Common Mistakes:

• Deleting the log file unnecessarily
• Using head -f which is invalid
• Restarting system without checking permissions

5. You want to monitor two log files live at the same time: /var/log/nginx/access.log and /var/log/nginx/error.log. Which command will correctly do this?

hard

A. tail -f /var/log/nginx/access.log /var/log/nginx/error.log

B. tail -f /var/log/nginx/access.log && tail -f /var/log/nginx/error.log

C. tail -f /var/log/nginx/access.log | tail -f /var/log/nginx/error.log

D. tail -f /var/log/nginx/access.log; tail -f /var/log/nginx/error.log

Solution

1. Step 1: Understand how to monitor multiple files

   tail -f accepts multiple filenames to follow them simultaneously in one terminal.

2. Step 2: Analyze each option

   tail -f /var/log/nginx/access.log /var/log/nginx/error.log correctly lists both files after tail -f. Using && or ; runs commands sequentially, so the second starts after the first ends. Piping two tail -f commands with | is invalid for this purpose.

3. Final Answer:

   tail -f /var/log/nginx/access.log /var/log/nginx/error.log -> Option A

4. Quick Check:

   Multiple files = list all after tail -f [OK]

Hint: List all files after tail -f to watch together [OK]

Common Mistakes:

• Using && or ; runs commands one after another, not together
• Piping two tail -f commands is invalid
• Trying to monitor files separately in one terminal