Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"lc-admin help" should always do #50

Closed
cschug opened this issue Sep 23, 2014 · 1 comment
Closed

"lc-admin help" should always do #50

cschug opened this issue Sep 23, 2014 · 1 comment

Comments

@cschug
Copy link

cschug commented Sep 23, 2014

I would expect lc-admin help to always print the usage information regardless whether a connection to log-courier can be made or not (actually I would furthermore expect that help prints that info only, not preforming any action).

# /etc/init.d/log-courier start
Starting log-courier:                                      [  OK  ]
# lc-admin help
Log Courier version 0.14 client

Attempting connection to unix:/var/lib/log-courier/admin.sock...
Connected

Available commands:
  reload    Reload configuration
  status    Display the current shipping status
  exit      Exit
# /etc/init.d/log-courier stop
Stopping log-courier:                                      [  OK  ]
# lc-admin help
Log Courier version 0.14 client

Attempting connection to unix:/var/lib/log-courier/admin.sock...
Failed to connect: dial unix /var/lib/log-courier/admin.sock: no such file or directory
@driskell
Copy link
Owner

Yes I agree.

In my head at the time I was considering sending the help command to the log-courier instance to list the commands. This way even if you upgraded only half the instances - you could use a single version (latest) of lc-admin to connect to any instance (even older version) and see commands available.

There's probably better more intuitive ways to reach that goal though than the current method!

Jason

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants