freebsd stable - Nov 2008 - kern.ipc.maxpipekva exceeded; see tuning(7)

I just got lots and lots of this:
    kern.ipc.maxpipekva exceeded; see tuning(7)

However, tuning(7) on my system has no information about this tunable 
whatsoever.

anglepoise:~ % uname -a
FreeBSD anglepoise.lon.incunabulum.net 7.1-PRERELEASE FreeBSD 
7.1-PRERELEASE #3: Tue Nov  4 15:40:44 GMT 2008     
root@anglepoise.lon.incunabulum.net:/home/obj/usr/src/sys/ANGLEPOISE7  amd64
anglepoise:~ % sysctl kern.ipc.maxpipekva
kern.ipc.maxpipekva: 20971520

I was running a couple of copies of "synergys" at the time. After 
killing them, all seems fine,  however this was causing most binaries on 
the system to error out with ENOMEM.

Any ideas?
BMS

I don't know off hand how you could end up with that many pipes.
Nonetheless, sys_pipe.c has a good explanation of what that does and
how pipe sizing works.

-Kip

On Thu, Nov 13, 2008 at 9:37 PM, Bruce Simpson <bms@incunabulum.net>
wrote:
> I just got lots and lots of this:
>   kern.ipc.maxpipekva exceeded; see tuning(7)
>
> However, tuning(7) on my system has no information about this tunable
> whatsoever.
>
> anglepoise:~ % uname -a
> FreeBSD anglepoise.lon.incunabulum.net 7.1-PRERELEASE FreeBSD
7.1-PRERELEASE
> #3: Tue Nov  4 15:40:44 GMT 2008
> root@anglepoise.lon.incunabulum.net:/home/obj/usr/src/sys/ANGLEPOISE7 
amd64
> anglepoise:~ % sysctl kern.ipc.maxpipekva
> kern.ipc.maxpipekva: 20971520
>
> I was running a couple of copies of "synergys" at the time. After
killing
> them, all seems fine,  however this was causing most binaries on the system
> to error out with ENOMEM.
>
> Any ideas?
> BMS
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
>


-- 
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis