landscape-config takes random arguments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I was ignorant and not watchign the manpage first.
I know 5 seconds later `landscape-config --disable` would be what I want.
But hey, this thing spoke about registering.
So I wanted to give it a try and go for man/--help if failing.
To my surprise, it behaved very different to what I expected.
Example:
root@m:~# landscape-config unregister
enabled
This script will interactively set up the Landscape client. It will
ask you a few questions about this computer and your Landscape
account, and will submit that information to the Landscape server.
After this computer is registered it will need to be approved by an
account administrator on the pending computers page.
Please see https:/
The computer title you provide will be used to represent this
computer in the Landscape user interface. It's important to use
a title that will allow the system to be easily recognized when
it appears on the pending computers page.
This computer's title []:
I'm surprised by two things:
1. I'd expect it to tell friendly me that "unregister" isn't a command it knows
2. And even more, why does landscape-config on an already registered system not tell me "sorry you are already attached"?
Up to you if you would want to change those, but I considered them worth reporting for you to think about.
Worth at least thinking about and smoothing out the UX. Backlogged.