RexOps / RexOps/Rex

Server options with -H

Open
#643 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
737
Forks
214
PR merge metrics
No merged PRs in 30d

Description

Server variable options are great but they are not honoured when you specify hosts with rex -H.
This is quite critical for example when rex is used in an multiuser environment.

Es:
set mpm_maxclients => "300"
group "web_hosting" =>
"web",
"web1" => { mpm_maxclients => "600"};

rex -G web_hosting task sets mpm_maxclients=600 for web1 as expected
rex -H "web web1" task sets mpm_maxclients=300 for both.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the discrepancy using the issue's rex -G and rex -H examples, comparing the server options applied to web and web1. Trace how host selection handles server variables in the -H and -G entry points, then verify that explicit hosts preserve per-host overrides while retaining group behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.