erroneous message from locked-up machine
Michael W. Lucas
mwlucas at blackhelicopters.org
Mon Nov 10 08:45:17 PST 2003
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 bewilderbeast kernel: kern.maxpipekva exceeded, please see tuning(7).
sysctl: unknown oid 'kern.maxpipekva'
And tuning(7) doesn't mention this, either.
Is this just work-in-progress, or did someone forget to commit something?
PS: Lesson of the day: no pipe KVA, no su. Great fun on remote
Michael Lucas mwlucas at FreeBSD.org, mwlucas at BlackHelicopters.org
Today's chance of throwing it all away to start a goat farm: 41.8%
Absolute OpenBSD: http://www.AbsoluteOpenBSD.com/
More information about the freebsd-current