We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using https://github.com/ganglia/gmond_python_modules/tree/master/gpfs to monitor gpfs aka Spectrum Scale 4.2.3
Upon the first call to mmpmon sudo is being called by root hence root is sudoing to root and hence not gaining the !requiretty flag.
Once its started the plugin is downgraded to ganglia and hence the !requiretty as in the readme file works.
If I add Defaults:root !requiretty or Defaults!/usr/lpp/mmfs/bin/mmpmon !requiretty it works fine.
Defaults:root !requiretty
Defaults!/usr/lpp/mmfs/bin/mmpmon !requiretty
This was found after quiet a bit of puzzeled looking around and needing to switch the debug options in sudo.
I'm thinking this is a security issue in how the plugin operate rather than just this one plugin and hence effects other plugins.
This is running Ganglia 3.7.2 under CentOs7.3 where ganglia runs as ganglia.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Using https://github.com/ganglia/gmond_python_modules/tree/master/gpfs to monitor gpfs aka Spectrum Scale 4.2.3
Upon the first call to mmpmon sudo is being called by root hence root is sudoing to root and hence not gaining the !requiretty flag.
Once its started the plugin is downgraded to ganglia and hence the !requiretty as in the readme file works.
If I add
Defaults:root !requiretty
or
Defaults!/usr/lpp/mmfs/bin/mmpmon !requiretty
it works fine.
This was found after quiet a bit of puzzeled looking around and needing to switch the debug options in sudo.
I'm thinking this is a security issue in how the plugin operate rather than just this one plugin and hence effects other plugins.
This is running Ganglia 3.7.2 under CentOs7.3 where ganglia runs as ganglia.
The text was updated successfully, but these errors were encountered: