'kern.maxpipekva exceeded' messages...
warlock at voip.kg
Mon Jan 19 21:01:05 PST 2004
On Tuesday 20 January 2004 04:06, Peter Losher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> In updating one of our authoritiative name servers to 5.2-REL, we
> enountered after two days of running, kernel message like:
> kern.maxpipekva exceeded, please see tuning(7).
> appearing to the point to where you couldn't ssh into the box (because sshd
> died w/ too many files opened). I see so mention of kern.maxpipekva on the
> tuning man page, and greping only finds kern.ipc entries.
> % sysctl -a | grep pipekva
> kern.ipc.maxpipekva: 10485760
> kern.ipc.maxpipekvawired: 5242880
> kern.ipc.pipekva: 131072
> kern.ipc.pipekvawired: 0
> Are they the same, and if so, what's are the guidelines for increasing the
Yes, you can sure if look in sys/kern/sys_pipe.c
In my case I just increased kern.ipc.maxpipekva in 16 times
Also I do not why there is any mention in tuning(7) about maxpipe (in 5.2
More information about the freebsd-current