Dealing with Server Commands

This document provides the information about running and managing Hugo server

🧩 Managing Multiple Site Processes on a Single Machine

When running multiple Hugo sites or similar services on one machine, it’s essential to monitor and manage active processes to avoid port conflicts, memory leaks, or zombie jobs.

🔍 Finding Running Jobs

Use ps and grep to locate processes:

1ps aux | grep hugo | grep -v grep

This lists all Hugo-related processes. Example output:

1user     12345  0.0  1.2 123456 7890 pts/0   S   12:34   0:01 hugo server --port 3300

• PID: Process ID (e.g. 12345)
• Command: What was launched
• Status: S (sleeping), R (running), T (stopped), Z (zombie)

🧠 Understanding Process States

🔪 Killing a Process

To terminate a process:

1kill <PID>

If it doesn’t respond:

1kill -9 <PID>

For zombie processes:

1. Identify the parent PID (usually a shell like sh -c)
2. Kill the parent:

1kill -9 <PARENT_PID>

🧼 Cleanup Script (Optional)

1ps aux | grep hugo | grep -v grep | awk '{print $2}' | xargs kill -9

Use with caution — this forcefully kills all Hugo-related jobs.

✅ Best Practices

• Use unique ports for each site (--port 3300, --port 3400, etc.)
• Log process launches for traceability
• Consider wrapping launches in Makefile targets or shell scripts

FAQs