You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the rationale for the suggested feature.
Very frequently users for get to run a host collect as root. This results in the collection simply reporting "permission denied" on files I need to be able to see.
Describe the feature
It would be good if at the HostCollector level either Troubleshoot automatically caught permission denied errors or at least could be user configurable to error on permission denied errors. While normally the project endeavors to complete collection regardless there are times when it would be better to just let the user know they have insufficient permissions so they can immediately rerun with the correct permissions.
The text was updated successfully, but these errors were encountered:
would it be sufficient to continue the collection, but issue warnings on stderr to the tune of "you should consider running this with sudo or as root in order to complete the collection, the result of this without permissions will be limited"?
Describe the rationale for the suggested feature.
Very frequently users for get to run a host collect as root. This results in the collection simply reporting "permission denied" on files I need to be able to see.
Describe the feature
It would be good if at the HostCollector level either Troubleshoot automatically caught permission denied errors or at least could be user configurable to error on permission denied errors. While normally the project endeavors to complete collection regardless there are times when it would be better to just let the user know they have insufficient permissions so they can immediately rerun with the correct permissions.
The text was updated successfully, but these errors were encountered: