Sat Jan 24 09:15:09 2015: Request 101662 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: PAR-Packer
Subject: Prevent shared libs from being cached in memory on AIX
Broken in: 1.024
Severity: Important
Owner: RSCHUPP
Requestors: th...@northpeak.org
Done.
https://rt.cpan.org/Ticket/Display.html?id=101662
Thanks
-Tim
On Wed, Jan 21, 2015 at 11:00 AM, Roderich Schupp <
roderich.sch...@googlemail.com> wrote:
> I see, weird.
> Your patch looks reasonable, shouldn't break in other environments as
> cache files should be in a per-user tree anywa
Wed Jan 21 12:09:40 2015: Request 101662 was acted upon.
Transaction: Ticket created by thoke
Queue: PAR-Packer
Subject: Prevent shared libs from being cached in memory on AIX
Broken in: 1.024
Severity: Important
Owner: Nobody
Requestors: th...@northpeak.org
I see, weird.
Your patch looks reasonable, shouldn't break in other environments as cache
files should be in a per-user tree anyway.
Just a file bug on RT against PAR-Packer (because that's were I look
first), the text of your original post should do.
Cheers, Roderich
Yes, you've got it. They remain loaded in memory even after the pp'd
binary has exited and been cleaned up (cache removed). The result is that
when the pp'd binary is called again (and again, and again), another copy
get's loaded (and kept) in memory because it's in a different cache
directory.
On Wed, Jan 21, 2015 at 5:00 PM, Tim Hoke wrote:
> On AIX, when I execute my pp'd binary (pp -C) the shared libs remain
> loaded in memory.
What do you mean by "remain loaded in memory" - even after the
process created by executing the pp'd binary has exited?
And why would changing the "other"
On AIX, when I execute my pp'd binary (pp -C) the shared libs remain loaded
in memory. I'd like to prevent that by changing the permissions on the
files in the cache. If the execute permissions are removed from 'other',
then the library won't be kept in memory on AIX.
Will this patch be sufficient
