To avoid the hardcoded memory limit you can install PECL packages with
# pear install pecl/
Given your examples with the providers above I think your declaration might
become
package{
"pear":
ensure => installed,
provider => 'pear';
"pecl/zip":
ensure => installed,
On Tuesday 03 Aug 2010 12:56:45 Trevor Hemsley wrote:
> No, it's not a clean solution but if the PECL maintainers are silly
> enough to hard code a memory limit in the shell script that is used to
> invoke it then there is not a huge amount that you can do about it.
> There are lots of hits on goo
No, it's not a clean solution but if the PECL maintainers are silly
enough to hard code a memory limit in the shell script that is used to
invoke it then there is not a huge amount that you can do about it.
There are lots of hits on google complaining about the hard coded memory
limit but not much
Quoting Trevor Hemsley :
When I look in my /usr/bin/pecl file I see that it is a 4 line shell
script and one of the parameters there sets the memory_limit. Did you
try hacking that?
I can see where in that file I could put the options, however the
whole point of us using puppet is that we don'
When I look in my /usr/bin/pecl file I see that it is a 4 line shell
script and one of the parameters there sets the memory_limit. Did you
try hacking that?
On 03/08/2010 12:16, li...@truthisfreedom.org.uk wrote:
> Hi all,
>
> I'm using the pear/pecl package providers from
> http://www.mit.edu/~m
Hi all,
I'm using the pear/pecl package providers from
http://www.mit.edu/~marthag/puppet/ and I've run into a memory limit
problem.
I've tried hacking the script so that it passes additional options to
pecl/pear, however these just error out about not being valid options
(even though t
