pcp
[Top] [All Lists]

Re: [pcp] PCP Updates: qa fallout from ipv6/unix sockets for pmlogger an

To: Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 20 Feb 2014 00:42:31 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5304D039.9010708@xxxxxxxxxx>
References: <52FE5058.4030702@xxxxxxxxxx> <53023D4E.1060504@xxxxxxxxxx> <y0mmwhoqu69.fsf@xxxxxxxx> <757832688.10280462.1392753861578.JavaMail.zimbra@xxxxxxxxxx> <896174788.10421447.1392770006295.JavaMail.zimbra@xxxxxxxxxx> <5304D039.9010708@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: h1P6VH1jiKFK93zgFtLgLX8a0psSRw==
Thread-topic: PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc

----- Original Message -----
> [...]
> On my system, PCP_TMP_DIR is /var/lib/pcp/tmp, which is where the
> pmlogger port map file is kept, and has the same issue as PCP_RUN_DIR,
> i.e. not writable by normal users.

*nod*, yep, understood.

> I think that ~/.pcp/pmlogger would be a good place.

The problem (which I failed to get across :) is that local pmloggers
are already writing to that location.  We would end up mixing up log
folios, per-host subdirectories, and so on with these new PID files.
Which would likely end in occassional wierd namespace conflicts, and
generally make management of these files more difficult.

Hence, the suggestion of ~/.pcp/tmp/pmlogger mirroring (a little, wrt
the suffix) the layout we're using for the system loggers port map.

> I don't see an existing environment variable for ~/.pcp. Systemtap uses
> SYSTEMTAPDIR, but PCPDIR doesn't seem to fit convention. How about
> PCP_USER_DIR. Any other suggestions?

Its $HOME/.pcp (aka QDir::homePath().append(".pcp") in the Qt code).

cheers.

--
Nathan

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