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). Interesting. bewilderbeast~;sysctl kern.maxpipekva sysctl: unknown oid 'kern.maxpipekva' bewilderbeast~; And tuning(7) doesn't mention this, either. Is this just work-in-progress, or did someone forget to commit something? ==ml PS: Lesson of the day: no pipe KVA, no su. Great fun on remote machines! :-) -- 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% http://www.BlackHelicopters.org/~mwlucas/ Absolute OpenBSD: http://www.AbsoluteOpenBSD.com/Received on Mon Nov 10 2003 - 07:45:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:28 UTC