On 02/20/2014 12:42 AM, Nathan Scott wrote:
----- Original Message -----
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.
The actual full name of the socket would be
~/.pcp/pmlogger/pmlogger.<pid>.socket. I don't see how this could end up
with a namespace conflict. Could you perhaps give an example? There is
some redundancy there. It could be shortened to
~/.pcp/pmlogger/<pid>.socket. Have said that, I'm not attached to my
choice, and it would be easy to add the extra tmp component.
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).
OK.
Overnight testing has revealed no qa issues. Once we agree on the
location of the socket, I can push the changes.
Dave
|