pcp
[Top] [All Lists]

Re: pmdagfs2: Improved distribution support and QA updates

To: Paul Evans <pevans@xxxxxxxxxx>
Subject: Re: pmdagfs2: Improved distribution support and QA updates
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 16 Jul 2013 19:35:05 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <51E57FB1.7050708@xxxxxxxxxx>
References: <51E57FB1.7050708@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 3DKzLQuwNMtZJA/CPd4iydDFS1anZA==
Thread-topic: pmdagfs2: Improved distribution support and QA updates
Hi Paul,

----- Original Message -----
> Changes commited to git://github.com/pauljevans/pcp.git dev
> ...
> commit 3818fd1f36ceae4fe2c48059a7ad475a62e524e9
> Author: Paul Evans <pevans@xxxxxxxxxx>
> Date:   Tue Jul 16 17:48:07 2013 +0100
> 
>      pmdagfs2: Install, set forced_restart=false
> 
>      Update Install for pmdagfs2 so that it no longer requires a restart of
>      pcp during the installation of the PMDA.

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.

> ...
>      on most installations with gfs2-utils present. Checked against Fedora
>      16-19, Ubuntu 13.04, Centos 6.4 and Debian 7 with Debian 7 being the
>      most restrictive through only having support for gfs2.glock metrics.

Wow - fantastic effort checking all those!

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>