Linux Bash脚本配置技术问询：开机自启、控制台启停及后台运行

Got it, let's tackle your three Bash script requirements one by one—these are super common use cases, so I'll walk you through practical, tested solutions that work on most modern Linux distros.

1. Auto-Start the Script on System Boot #

The most reliable way these days is using systemd (the default init system for Ubuntu, Fedora, Debian 10+, etc.). If you're on an older distro with SysVinit, I'll also include a crontab fallback.

Systemd Method #

• First, create a systemd service file for your script. Open a text editor with sudo:

  sudo nano /etc/systemd/system/your_script.service
  

• Paste this content, replacing placeholders with your actual script path and details:

  [Unit]
  Description=My Custom Bash Script
  After=network.target  # Adjust if your script needs other services first
  
  [Service]
  ExecStart=/path/to/your/script.sh
  Restart=always  # Optional: restarts the script if it crashes
  User=your_username  # Run as your user instead of root (safer)
  WorkingDirectory=/path/to/script/directory  # Optional: set working dir
  
  [Install]
  WantedBy=multi-user.target
  

• Save the file, then reload systemd to recognize the new service:

  sudo systemctl daemon-reload
  

• Enable auto-start on boot:

  sudo systemctl enable your_script.service
  

• You can start it immediately with:

  sudo systemctl start your_script.service
  

Crontab Fallback #

If systemd isn't an option, use @reboot in crontab:

• Open your user's crontab:

  crontab -e
  

• Add this line (replace with your script path):

  @reboot /path/to/your/script.sh > /dev/null 2>&1 &
  

• The > /dev/null 2>&1 silences output, and & runs it in the background.

2. Control the Script via Console (Start/Stop/Restart) #

Add a simple command-line interface to your script using a case statement. Here's how to modify your script:

• Open your script in an editor:

  nano /path/to/your/script.sh
  

• Add this at the top (before your main script logic):

  #!/bin/bash
  
  # Define the PID file to track the script's process
  PID_FILE="/tmp/your_script.pid"
  
  case "$1" in
    start)
      if [ -f "$PID_FILE" ] && kill -0 $(cat "$PID_FILE") 2>/dev/null; then
        echo "Script is already running."
        exit 1
      fi
      # Start the script in the background (adjust this to your main command)
      /path/to/your/script_main_logic.sh > /dev/null 2>&1 &
      echo $! > "$PID_FILE"
      echo "Script started successfully."
      ;;
    stop)
      if [ ! -f "$PID_FILE" ] || ! kill -0 $(cat "$PID_FILE") 2>/dev/null; then
        echo "Script is not running."
        exit 1
      fi
      kill $(cat "$PID_FILE")
      rm "$PID_FILE"
      echo "Script stopped successfully."
      ;;
    restart)
      "$0" stop
      sleep 2
      "$0" start
      ;;
    *)
      echo "Usage: $0 {start|stop|restart}"
      exit 1
      ;;
  esac
  

• Replace /path/to/your/script_main_logic.sh with your actual script code (or move your existing logic into a separate section after this case statement).
• Make the script executable:

  chmod +x /path/to/your/script.sh
  

• Now you can control it via console:

  ./script.sh start
  ./script.sh stop
  ./script.sh restart
  

3. Keep the Script Running After Closing the Console #

There are a few ways to handle this, depending on how you're starting the script:

If Using Systemd (Recommended) #

Systemd automatically runs services in the background, even if you close the console. The service we set up earlier already takes care of this—no extra steps needed.

If Using the Console Control Script #

Modify the start case in your script to use nohup or setsid to detach the process from the terminal:

• Update the start line to:

  nohup /path/to/your/script_main_logic.sh > /dev/null 2>&1 &
  

  Or use setsid for even better detachment:

  setsid /path/to/your/script_main_logic.sh > /dev/null 2>&1 &
  

• nohup ignores the "hangup" signal sent when you close the terminal, so the script keeps running.

One-Off Manual Start #

If you ever need to start the script manually and keep it running after closing the console, use:

nohup ./script.sh > /dev/null 2>&1 &

Or use screen/tmux if you want to reattach to the script's output later, but nohup is simpler for persistent background runs.

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