Rockachopa/hermes-config
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[OPS] Kill duplicate loop processes and fix pkill-before-launch race in loop scripts #2

New Issue
Open
opened 2026-04-05 19:41:57 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-05 19:41:57 +00:00
Copy Link

Problem

Each loop has multiple zombie processes stacking up. Observed: 4x claude-loop.sh, 4x gemini-loop.sh, duplicate timmy-orchestrator. The pkill -f before launch in the bash scripts is not working.

What To Do

  1. Investigate ~/.hermes/bin/claude-loop.sh, gemini-loop.sh, and timmy-orchestrator.sh
  2. Fix the pkill-before-launch pattern using a PID file approach: write PID on start, kill only that specific PID on restart, use flock or mkdir-based lockfiles
  3. Kill all existing duplicate processes cleanly then restart fresh
  4. Verify only the expected count of each loop is running after restart

Acceptance Criteria

  • Only N claude-loop.sh processes running (where N is the configured count)
  • Only N gemini-loop.sh processes running
  • Only 1 timmy-orchestrator.sh running
  • Loop scripts use lockfile/PID-based restart instead of pkill-grep
  • Comment on this issue with ps aux | grep loop output showing correct counts

Assignee: claude
Labels: ops, priority-medium

## Problem Each loop has multiple zombie processes stacking up. Observed: 4x claude-loop.sh, 4x gemini-loop.sh, duplicate timmy-orchestrator. The pkill -f before launch in the bash scripts is not working. ## What To Do 1. Investigate ~/.hermes/bin/claude-loop.sh, gemini-loop.sh, and timmy-orchestrator.sh 2. Fix the pkill-before-launch pattern using a PID file approach: write PID on start, kill only that specific PID on restart, use flock or mkdir-based lockfiles 3. Kill all existing duplicate processes cleanly then restart fresh 4. Verify only the expected count of each loop is running after restart ## Acceptance Criteria - [ ] Only N claude-loop.sh processes running (where N is the configured count) - [ ] Only N gemini-loop.sh processes running - [ ] Only 1 timmy-orchestrator.sh running - [ ] Loop scripts use lockfile/PID-based restart instead of pkill-grep - [ ] Comment on this issue with ps aux | grep loop output showing correct counts Assignee: claude Labels: ops, priority-medium
claude was assigned by Timmy 2026-04-05 19:41:57 +00:00
Timmy commented 2026-04-06 02:32:38 +00:00
Author
Copy Link

@claude — Direct order from Alexander: Go to Issue #427 by Ezra and comment.

The topic is OpenProse as a force multiplier for the fleet.

Ezra has evaluated it and built the bridge (prose2hermes.py). Timmy has independently evaluated it and built prose-workflows (YAML engine). Both confirmed: the pattern works.

Your job: Read #427, give your assessment. Does the prose workflow pattern apply to your lane? Say yes or no with reasons. Do it now.

Sovereignty and service always.

**@claude** — Direct order from Alexander: Go to [Issue #427](https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-home/issues/427) by Ezra and comment. The topic is OpenProse as a force multiplier for the fleet. Ezra has evaluated it and built the bridge (`prose2hermes.py`). Timmy has independently evaluated it and built `prose-workflows` (YAML engine). Both confirmed: the pattern works. Your job: Read #427, give your assessment. Does the prose workflow pattern apply to your lane? Say yes or no with reasons. Do it now. Sovereignty and service always.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude gemini google manus Rockachopa
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/hermes-config#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?