Re: Re: caRepeater question

["J. Lewis Muir via Core-talk" <core-talk at aps.anl.gov>]

On 01/31, Zimoch Dirk via Core-talk wrote:
> The situation I have in mind: caRepeater is *not* running as a service. First
> caClient starts it. Second client by another user finds the fist users
> caRepeater and uses it. First user logs out or whatever and kills all its
> processes. What happens with the second user's caClient?

Hi, Dirk!

I run caRepeater as a minimal-privilege user as a service that gets
started at boot time.  I know you said it's not running as a service,
but why not?  I never liked the idea of a user using the caRepeater
process of another user.  IMO, that's just asking for trouble (the
reason you gave is one example) and doesn't adhere to POLA.

A bit of a thread hijack, but is caRepeater still needed these days?  I
have never liked it, and a library (ca) that starts another process on
demand is really ugly, IMO.  (And I think it might even need caRepeater
in the search path of whatever program is using the library because the
library doesn't use an absolute path to it?  I can't remember; might be
wrong about that.  But if it does, that's really ugly too.)  Isn't there
a way around needing caRepeater by now?

Regards,

Lewis