Bug 787250 - [rhq-agent-env.sh/bat] --daemon should not be in example value for RHQ_AGENT_CMDLINE_OPTS and comment should be added saying --daemon should generally *not* be included in RHQ_AGENT_CMDLINE_OPTS
Summary: [rhq-agent-env.sh/bat] --daemon should not be in example value for RHQ_AGENT_...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-03 17:04 UTC by Ian Springer
Modified: 2013-08-06 00:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:24:10 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 768707 0 medium CLOSED Passing agent command-line options via start script/environment prevents agent from starting as normal 2021-02-22 00:41:40 UTC

Internal Links: 768707

Description Ian Springer 2012-02-03 17:04:53 UTC 
Due to the fact that rhq-agent-env.sh is used by both
rhq-agent-wrapper.sh and rhq-agent.sh, users should never include --daemon when
setting RHQ_AGENT_CMDLINE_OPTS in rhq-agent-env.sh. Including it there would cause the Agent to always start in daemon mode, even when started via rhq-agent.sh, which generally wouldn't make sense, since rhq-agent-wrapper.sh is the recommended way to start the Agent as a daemon.

We should remove it from the commented out "#RHQ_AGENT_CMDLINE_OPTS=" line in the default rhq-agent-env.sh and add a comment telling users to never include --daemon in the value.
Comment 1 Ian Springer 2012-02-03 19:07:19 UTC 
This is done in master - http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=0ed38f2
Comment 2 Mike Foley 2012-02-07 19:24:10 UTC 
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
Note You need to log in before you can comment on or make changes to this bug.