The other last issue I could find is that if the switch to non-root happens after the client has been running for a while in the traditional root mode, at least the watchdog.log log file would be owned by root, making the client crash when starting in non-root mode because of lack of write access to that file.
I also tested custom graphs with the client in non-root mode, and, using trunk on the server side, got the expected error of having script execution disabled on the client.
The other last issue I could find is that if the switch to non-root happens after the client has been running for a while in the traditional root mode, at least the watchdog.log log file would be owned by root, making the client crash when starting in non-root mode because of lack of write access to that file.
I also tested custom graphs with the client in non-root mode, and, using trunk on the server side, got the expected error of having script execution disabled on the client.
qa + 1 other than the log issue.