pcp
[Top] [All Lists]

Re: pmlc access control, was Re: PCP Updates: qa fallout from ipv6/unix

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: pmlc access control, was Re: PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc
From: fche@xxxxxxxxxx (Frank Ch. Eigler)
Date: Thu, 20 Feb 2014 17:13:41 -0500
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <53067159.9050409@xxxxxxxxxxxxxxxx> (Ken McDonell's message of "Fri, 21 Feb 2014 08:19:21 +1100")
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> <1347098955.12246278.1392874951684.JavaMail.zimbra@xxxxxxxxxx> <530612EC.8020206@xxxxxxxxxx> <y0meh2xmtb9.fsf_-_@xxxxxxxx> <53067159.9050409@xxxxxxxxxxxxxxxx>
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
Ken McDonell <kenj@xxxxxxxxxxxxxxxx> writes:

> [...]  I believe pmlc use is very rare, probably because I have not
> managed to convince anyone else that the "value add" proposition for
> pmlc in the following scenario is real: [...]

I very much believe in that scenario!  I'm just not sure whether it's
best done within pmie vice within a more clever pmlogger.  An extra
complication is that pmie requires a second connection to pmcd (a
temporary one at that, repeatedly suffering startup costs); it cannot
piggy-back on an archive being written-to by pmlogger.

- FChE

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