Linux下如何将Bash脚本最新日志存储在文件顶部？

Got it, let's tackle this problem—you want your script's output to land at the top of the log file instead of the default bottom, while keeping your existing file descriptor setup (saving/restoring stdout/stderr) intact. Here's how to adjust your script:

First, Let's Recap Your Existing Setup #

Your current code saves the original stdout (file descriptor 3) and stderr (file descriptor 4), then uses a trap to restore them when the script exits. That's a solid foundation—we just need to modify where the output goes so it prepends to the log instead of appending.

Modified Script Header #

Replace your existing exec/trap lines with this (update LOG_FILE to your actual log path):

#!/bin/bash
LOG_FILE="/var/log/your_script.log"

# Save original stdout and stderr to file descriptors 3 and 4
exec 3>&1 4>&2

# Redirect stdout to a process that prepends each line to the log
exec 1> >(while IFS= read -r line; do
    # Insert the line at the FIRST line of the log file
    sed -i "1i $line" "$LOG_FILE"
    # Optional: Print the line to the original stdout (so you see it in the terminal)
    echo "$line" >&3
done)

# Redirect stderr similarly (add [ERROR] tag for clarity)
exec 2> >(while IFS= read -r line; do
    sed -i "1i [ERROR] $line" "$LOG_FILE"
    # Optional: Print errors to original stderr
    echo "[ERROR] $line" >&4
done)

# Restore original descriptors and clean up when script exits
trap 'exec 2>&4 1>&3; exec 3>&- 4>&-' EXIT

How This Works #

• Process Substitution: The >(...) syntax sends stdout/stderr to a background loop that processes each line in real time.
• sed -i "1i $line": This tells GNU sed (default on Linux) to insert (i) the line at line 1 of the log file, effectively putting new content at the top.
• IFS= read -r line: Ensures we handle lines with spaces, tabs, or special characters correctly without truncation.
• Optional Terminal Output: The echo "$line" >&3 lines let you still see the script's output in your terminal while it's being logged—remove these if you only want output in the log file.

Important Notes #

1. Performance for Large Logs: If your log file grows very large, using sed -i every time will slow things down (since sed has to rewrite the entire file for each line). For high-volume logs, consider this alternative:

   • Write all output to a temporary file first
   • At script exit, prepend the temp file to your main log:

     TEMP_LOG=$(mktemp)
     exec 1>"$TEMP_LOG" 2>&1
     # ... rest of your script ...
     trap 'cat "$TEMP_LOG" "$LOG_FILE" > "$LOG_FILE.tmp" && mv "$LOG_FILE.tmp" "$LOG_FILE"; rm "$TEMP_LOG"; exec 2>&4 1>&3' EXIT
     

   This is faster for large logs but only updates the main log once when the script finishes.

2. GNU sed vs BSD sed: On Linux, sed -i works without a backup suffix. If you ever run this on macOS/BSD, you'll need to add a backup suffix (e.g., sed -i.bak "1i $line"), then delete the .bak file afterward.

3. Error Handling: The [ERROR] tag in the stderr redirect helps you distinguish regular output from errors at a glance—feel free to adjust or remove it.

内容的提问来源于stack exchange，提问作者Mansoor