Re: erroneous message from locked-up machine

2003-11-11 Thread Terry Lambert
Alex Wilkinson wrote: > Can someone please elaborate on the acronym KVA ? > > $ sysctl -d kern.ipc.maxpipekva > kern.ipc.maxpipekva: Pipe KVA limit > > This doesn't tell me enough. Kernel Virtual Address The fast pipe code in FreeBSD uses page lending between the processes participating in the

Re: erroneous message from locked-up machine

2003-11-11 Thread Dag-Erling Smørgrav
Alex Wilkinson <[EMAIL PROTECTED]> writes: > Can someone please elaborate on the acronym KVA ? Kernel virtual address space DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/free

Re: erroneous message from locked-up machine

2003-11-10 Thread Alex Wilkinson
Can someone please elaborate on the acronym KVA ? $ sysctl -d kern.ipc.maxpipekva kern.ipc.maxpipekva: Pipe KVA limit This doesn't tell me enough. - aW On Tue, Nov 11, 2003 at 04:46:47AM +1100, Bruce Evans wrote: > > I came in to work today to find one of my -current machine

Re: erroneous message from locked-up machine

2003-11-10 Thread Bruce Evans
On Mon, 10 Nov 2003, Michael W. Lucas wrote: > I came in to work today to find one of my -current machines unable to > open a pipe. (This probably had a lot to do with the spamd that went > stark raving nutters overnight, but that's a separate problem.) A > power cycle fixed the problem, but /va

Re: erroneous message from locked-up machine

2003-11-10 Thread Alexander Leidinger
On Mon, 10 Nov 2003 11:45:13 -0500 "Michael W. Lucas" <[EMAIL PROTECTED]> wrote: > Nov 10 11:05:44 bewilderbeast kernel: kern.maxpipekva exceeded, please see tuning(7). > > Interesting. > > bewilderbeast~;sysctl kern.maxpipekva > sysctl: unknown oid 'kern.maxpipekva' > bewilderbeast~; sysctl ke

erroneous message from locked-up machine

2003-11-10 Thread Michael W. Lucas
I came in to work today to find one of my -current machines unable to open a pipe. (This probably had a lot to do with the spamd that went stark raving nutters overnight, but that's a separate problem.) A power cycle fixed the problem, but /var/log/messages was filled with: Nov 10 11:05:44 bewil