User story #8076
closed
rudder agent status/start/stop
Added by Alexander Brunhirl over 8 years ago.
Updated about 8 years ago.
Description
Hi,
maybe this would be a useful feature to implement a "status" into the `rudder` command.
So all relevant command stick together, instead of using the "/etc/init.d/rudder-agent status".
ltrudder:~ # docker exec rudder_c01 rudder agent status
rudder-agent[28451]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[28454]: [INFO] Using /var/rudder/cfengine-community for CFEngine workdir
rudder-agent[28457]: [INFO] All configured CFEngine Community processes are running
ltrudder:~ #
Regards,
Alex
- Assignee set to Benoît PECCATTE
- Priority changed from N/A to 3
- Target version changed from Ideas (not version specific) to 4.0.0~rc2
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/53
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Subject changed from rudder agent status to rudder agent status/start/stop
- Target version changed from 4.0.0~rc2 to 318
- Target version changed from 318 to 4.0.0~rc2
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Also available in: Atom
PDF