Comment 6 for bug 82159

So these are my other findings.

a) running landscape-config erases the non-root configuration from /etc/landscape/client.conf. /etc/default/landscape-client stays the same.

b) the following actions/monitoring functions stop working (probably expected, so I mention them just for completeness):
- custom graphs
- script execution
- package operations
- process killing
- user management
- viewing user locked or not locked status: it's assumed they are always unlocked
- restart/shutdown

c) the error message that is displayed when one of the above is tried is confusing, because it's a generic error message that states many possible causes for the error. If possible, we should try to give a precise message about why the error happened (the client is in non-root and read-only mode).