| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] Secure sockets builds have high daemon memory utilisation |
| From: | Dave Brolley <brolley@xxxxxxxxxx> |
| Date: | Tue, 10 Jun 2014 15:19:28 -0400 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <5397573A.90102@xxxxxxxxxx> |
| References: | <1896810420.23212457.1402370819966.JavaMail.zimbra@xxxxxxxxxx> <5397573A.90102@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 |
On 06/10/2014 03:06 PM, Dave Brolley wrote: I just had the thought that, unless we get into the game of unloading these libraries when no longer in use (i.e. dlcose(3)), then after the first secure connection is made, the RSS will be permanently increased anyway.On 06/09/2014 11:26 PM, Nathan Scott wrote:[ ... ] given that most people wont be using encryption/non-af_unix authentication at all. I wonder if we could get crafty and load the secure sockets support in an "on-demand" fashion? We do have both forms of networking still there in the code of course - could we find a way to bootstrap in the security libs only if they are actually needed? (i.e. run time linking, via dlopen(3) trickery, instead of compile time linking). Dave |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Secure sockets builds have high daemon memory utilisation, Dave Brolley |
|---|---|
| Next by Date: | Re: PCP web client on different domain, Frank Ch. Eigler |
| Previous by Thread: | Re: Secure sockets builds have high daemon memory utilisation, Dave Brolley |
| Next by Thread: | Re: Secure sockets builds have high daemon memory utilisation, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |