Date: Sun, 21 Dec 1997 05:31:25 -0500 (EST) From: "John S. Dyson" <dyson@FreeBSD.ORG> To: dyson@FreeBSD.ORG Cc: scrappy@thelab.hub.org, freebsd-current@FreeBSD.ORG Subject: Re: Strange behaviour with -current kernel... Message-ID: <199712211031.FAA04495@dyson.iquest.net> In-Reply-To: <199712210922.EAA00967@dyson.iquest.net> from "John S. Dyson" at "Dec 21, 97 04:22:17 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Following up my own message, found out that -current has a bug that can be fixed by code that I already have in my tree. Will commit ASAP. Also, for now, feel free to use the sysctl below. John S. Dyson said: > The Hermit Hacker said: > > > > I've just upgraded to the most current kernel, and am having some very, > > very strange problems with my system. I use pine for email, and each time > > I restart pine, it tells me that its a new version (haven't upgraded pine > > in months) and regenerates my .pinerc. Looking at the .pinerc itself > > seems to show some "weird" stuff: > > > Probably my fault. Try setting either (depending what is in -current): > > sysctl -w debug.ioopt=0 > or > sysctl -w vfs.ioopt=0 > > If this fixes it, I'll disable the code by default. Sorry... :-(. > -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712211031.FAA04495>