I have upgrade 70.8 to 70.10 and I get this error try usind a diskd in squid
a squid try restart but continues not work.
I version 70.8 diskd work ok. not get any this errors, I try in a another
machine.
I belive is a diskd options is not include or not correct configured in kernel.
optio
If you really are running a setup that requires this type of
modification then I would suggest running the squid process on another
machine and redirect all HTTP connections to the 2nd box using the
port forward screen under nat.
Our Squid package is meant to be "easy" and require no user interven
from what I can read in the squid faq your kernel need to get rebuilt.
http://www.squid-cache.org/Doc/FAQ/FAQ-22.html#ss22.6
"The messages between Squid and diskd are 32 bytes for 32-bit CPUs and
40 bytes for 64-bit CPUs. Thus, MSGSSZ should be 32 or greater. You
may want to set it to a larger val
Alright, I'll recompile the kernel with:
options MSGMNB=8192 # max # of bytes in a queue
options MSGMNI=40 # number of message queue identifiers
options MSGSEG=512 # number of message segments per queue
options MSGSSZ=6
Are we having a kernel compiled specifically for squid
diskd support here?
Can we not just put the appropriate sysctl tunable
values in /boot/loader.conf and then reboot to effect
the changes?
Best regards,
Miles
--- Scott Ullrich <[EMAIL PROTECTED]> wrote:
> Alright, I'll recompile the kern
Uhhh, what's that gonna do to the rest of us that don't use squid? Is
this going to make the kernel use more memory?
--Bill
On 7/24/05, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> Alright, I'll recompile the kernel with:
>
> options MSGMNB=8192 # max # of bytes in a queue
>
I will look into using the sysctl.conf infrastructure that we have.
I have a feeling that some of these values need to be passed from the
boot loader, however. We'll see.
Scott
On 7/25/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
> Uhhh, what's that gonna do to the rest of us that don't use
