http://defect.opensolaris.org/bz/show_bug.cgi?id=11187
Renee Danson Sommerfeld <renee.danson at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ACCEPTED
CC| |renee.danson at sun.com
--- Comment #2 from Renee Danson Sommerfeld <renee.danson at sun.com>
2009-09-10 00:28:08 UTC ---
(In reply to comment #1)
> I think the reason for the error message is because the location was enabled
> automatically. It is not possible to disable this location in this case. If
> the location was enabled manually even if it is conditional, then only the
> manual disable is allowed. Correct?
Yes. Another way of saying that is, you can only explicitly disable a location
that you explicitly enabled.
You could *implicitly* disable this location by enabling a different one.
But the bottom line is, the behavior is correct. However, Lizhong's point that
the message is confusing is also valid. I think there are two problems: first,
it says "Could not enable..." when it should be "Could not disable..."; second,
the "entity is in incorrect state", while technically true, is not very
helpful.
Maybe something like "Could not disable loc 'loc0': entity was automatically
enabled, cannot be manually disabled"?
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
