CampaignManager: avoid parameter-name clash
The -p parameter is already being used by several campaign servers for
the prune method to restrict to (which was broken in commit
6c120004e), hence allow only --port to choose a different server TCP
port at runtime.
Change-Id: Ia30e40d564e85a9702118dc28df4988ec628e491
This commit is contained in:
@ -29,8 +29,8 @@ public:
|
|||||||
CampaignManager() : m_jobserver(0), m_currentCampaign(0)
|
CampaignManager() : m_jobserver(0), m_currentCampaign(0)
|
||||||
{
|
{
|
||||||
fail::CommandLine &cmd = fail::CommandLine::Inst();
|
fail::CommandLine &cmd = fail::CommandLine::Inst();
|
||||||
port = cmd.addOption("p", "port", Arg::Required,
|
port = cmd.addOption("", "port", Arg::Required,
|
||||||
"-p,--port \tListening port of server; no "
|
"--port \tListening port of server; no "
|
||||||
"value chooses port automatically");
|
"value chooses port automatically");
|
||||||
}
|
}
|
||||||
~CampaignManager();
|
~CampaignManager();
|
||||||
|
|||||||
Reference in New Issue
Block a user