Hi Nathan,
On 07/17/2013 12:35 AM, Nathan Scott wrote:
It's my (current) understanding that pmdagfs2 must run as root, in order to
access the trace and other debugfs files it uses - is that correct?
If it is, we must keep forced_restart set to true. Otherwise the ./Install
process will use a SIGHUP to notify pmcd of the new PMDA, which results in
the PMDA being started under the unprivileged "pcp" user account. A restart
allows agents to run as root but opt out and run unprivileged if they choose
to. The latter is preferred, but naturally its not always possible.
Hopefully its OK to run pmdagfs2 not-as-root - if so, this change is fine.
After checking some more this morning, it appears running in
unprivileged mode does not affect any of the tracing for the metrics,
however it breaks pmstore for the gfs2.control.glock_lock_time metric as
it is now unable to write to the trace-point enable file (needs root).
This is a bit of an oversight on my behalf, only checked the metrics not
pmstore :S. It looks like the pmda will have to run privileged for now,
I shall roll back that last commit on my end.
Cheers,
Paul.
|