[EMAIL PROTECTED] writes:
> Each worker proces has a child process unless i'm wrong ;)
No. There is one parent process and one child process. The worker
threads are just that - threads.
DES
--
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no
_
Each worker proces has a child process unless i'm wrong ;)
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
[EMAIL PROTECTED] writes:
> maybe can i decrease value of workers and increase value of child
> process...
I don't know what you mean by "increase value of child process".
DES
--
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no
_
maybe can i decrease value of workers and increase value of child process ...
is there any chance to do it ?
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
[EMAIL PROTECTED] writes:
> i don't know if it's logic...i just try everythink ... is there any
> possibility to cache object in RAM ?
Varnish caches objects in virtual memory, and leaves it up to the kernel
to decide whether this means RAM or swap.
> If not then can you tell waht should i do rem
i don't know if it's logic...i just try everythink ... is there any possibility
to cache object in RAM ? If not then can you tell waht should i do remove this
error ...
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpr
[EMAIL PROTECTED] writes:
> ulimit -n 5 :)
Where is the logic in this? You run out of address space, and respond
by increasing the number of file descriptors?
DES
--
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no
___
varni
ulimit -n 5 :)
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
"ADOFMS Admin, SteveOC" <[EMAIL PROTECTED]> writes:
> Correct me if Im wrong - but is it possible to address more than 4GB of
> RAM with a 32bit linux kernel ?
Provided your kernel was built with PAE support, yes, but the process
address space is still limited to 3 GB.
DES
--
Dag-Erling Smørgrav
[EMAIL PROTECTED] wrote:
> i686 GNU/Linuxi have also set the ulimit value as 50...and worker
> proces 2048 but still the same error
> ___
> varnish-misc mailing list
> varnish-misc@projects.linpro.no
> http://projects.linpro.no/mailman/listinfo/
[EMAIL PROTECTED] writes:
> i686 GNU/Linux
The i386 has a 4 GB address space, 1 GB of which is normally reserved
for the kernel, leaving 3 GB for applications (or even less depending on
the data segment size limit, 'ulimit -d'). A big chunk of that goes to
the program text (including librarie
i686 GNU/Linuxi have also set the ulimit value as 50...and worker
proces 2048 but still the same error
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
[EMAIL PROTECTED] writes:
> This message i receive when my varnish run. I have 6 GB of RAM but
> when i run varnish 5 GB are free ... the 1 GB is for somethink another
> ...not for varnishso what can i do to tell varnish using RAM ??
You are most likely running out of address space. What plat
This message i receive when my varnish run. I have 6 GB of RAM but when i run
varnish 5 GB are free ... the 1 GB is for somethink another ...not for
varnishso what can i do to tell varnish using RAM ??
___
varnish-misc mailing list
varnish-misc@proj
jean-marc pouchoulon <[EMAIL PROTECTED]> writes:
> varnish was stopped with this error:
>
> 0 CLIRd ping
> 0 CLIWr 0 200 PONG 1183565922
> 0 Debug "Create worker thread failed 12 Cannot allocate memory"
> 0
Helo,
varnish was stopped with this error:
0 CLIRd ping
0 CLIWr 0 200 PONG 1183565922
0 Debug "Create worker thread failed 12 Cannot allocate memory"
0 CLIRd ping
0 CLIWr 0 200 PONG 1183565925
0 Debug
16 matches
Mail list logo
