searxng-mcp-go/searxng-server-test/lib-searxng-pid.sh
XLion e5066e1a8a
review: address CodeRabbit feedback
- Tighten granian process matching: use 'searx.webapp:app' instead of
  'granian' in lib-searxng-pid.sh, 02-stop.sh, 03-status.sh, and docs
- Fix hardcoded port in 01-start-fg.sh URL echo
- Update outdated comment in 00-setup.sh (deps come from uv sync, not
  requirements files)
- Add inline comments for non-pinned deps in pyproject.toml
2026-06-13 00:42:44 +08:00

24 lines
1,007 B
Shell
Executable file

#!/usr/bin/env bash
# Shared helpers for the background SearXNG test server scripts.
# This file is meant to be sourced (not executed) by:
# - 01-start-bg.sh
# - 02-stop.sh
# - 03-status.sh
#
# Keeping a single source of truth avoids drift between the three scripts
# when the PID ownership contract changes.
# is_searxng_pid <pid>
# Return 0 if <pid> is alive AND its argv contains 'searx/webapp.py' or 'searx.webapp:app'.
# Return 1 otherwise (process gone, recycled, or unrelated).
#
# This guards against a classic Unix pitfall: a PID recorded on disk can be
# recycled by an unrelated process between writes. Treating the recycled PID
# as "our SearXNG" would let stop/status scripts SIGTERM/SIGKILL a stranger
# or report a false live state, and would block a clean re-start.
is_searxng_pid() {
local pid="$1"
[ -n "$pid" ] || return 1
ps -p "$pid" -o args= 2>/dev/null | grep -Fq 'searx/webapp.py' || \
ps -p "$pid" -o args= 2>/dev/null | grep -Fq 'searx.webapp:app'
}