Date: Fri, 15 May 1998 08:21:25 +0100 From: Brian Somers <brian@Awfulhak.org> To: Open Systems Networking <opsys@mail.webspan.net> Cc: Brian Feldman <brianfeldman@hotmail.com>, freebsd-current@FreeBSD.ORG Subject: Re: SoftUpdates stable?? Message-ID: <199805150721.IAA08488@awfulhak.org> In-Reply-To: Your message of "Thu, 14 May 1998 20:33:22 EDT." <Pine.BSF.3.95.980514202312.16839C-100000@orion.webspan.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Same problems here - I have /tmp async and not soft-updated. The rest is soft-updated and not async. The locks under X are quick & bad (about 10-15 minutes after starting X) - not even BREAK on a serial console gets a look-in. > On 14 May 1998, Brian Feldman wrote: > > > Get used to it. <g> > It just happened to me about 15 minutes ago, I Cannot for the life of me > get Soft Updates to play nice with X. > I was running xlock as well, xlock -fullrandom -inroot -ncolors 200 -mode ifs > heh cause I have CPU to burn :) > Softupdates does not like X. I dont know why. But it seems to be a "leak" > Meaning it runs fine for a few hours but after that i have never been able > to get 5 days uptime, so after a few hours and before 5 days it ALWAYS > wedges with SU. I dont have a serial console so this is all speculation > and worthless info. But like I said its like something leaks, its fine for > a few hours under X, but the longer it goes the higher the chance of a > wedge. and it NEVER makes it to 5 days of uptime for me anyway. > So I play with new releases julian makes but then when it wedges I go back > to non-SU kernels. It will all get worked out in due time. > > Chris > > -- > "I don't do favors, I accumulate debts" > > ===================================| Open Systems Networking And Consulting. > FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 > -----------------------------------| 1402 N. Washington, Wellington, KS-67152 > FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net > http://www.freebsd.org | Consulting-Network Engineering-Security > ===================================| http://open-systems.net > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: 2.6.2 > > mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te > gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC > foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z > d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb > NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv > CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 > b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= > =BBjp > -----END PGP PUBLIC KEY BLOCK----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org> <http://www.Awfulhak.org>; Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805150721.IAA08488>