You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ bin/agent status
Starting supervisor
2013-05-21 11:47:47,894 INFO RPC interface 'supervisor' initialized
2013-05-21 11:47:47,894 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2013-05-21 11:47:47,895 INFO supervisord started with pid 98048
2013-05-21 11:47:48,897 INFO spawned: 'dogstatsd' with pid 98052
2013-05-21 11:47:48,899 INFO spawned: 'forwarder' with pid 98053
2013-05-21 11:47:48,902 INFO spawned: 'collector' with pid 98054
...
Once you ctrl-c out, it will run the actual command.
I think that lines 7 to 14 of /bin/agent should be moved into the $action case statement, under the start command (currently line 24).
The text was updated successfully, but these errors were encountered:
So is this intended functionality? This is different from how it works on deb and redhat, where running status will simply tell you if the agent is running. I know that some users would want to use the status command in configuration management tools, so we should try to be consistent across different packaging.
Once you ctrl-c out, it will run the actual command.
I think that lines 7 to 14 of
/bin/agent
should be moved into the$action
case statement, under the start command (currently line 24).The text was updated successfully, but these errors were encountered: