From owner-freebsd-current Fri May 15 01:33:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07324 for freebsd-current-outgoing; Fri, 15 May 1998 01:33:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07319 for ; Fri, 15 May 1998 01:33:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA10181; Fri, 15 May 1998 01:24:36 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010179; Fri May 15 08:24:32 1998 Date: Fri, 15 May 1998 01:24:28 -0700 (PDT) From: Julian Elischer To: Brian Somers cc: Open Systems Networking , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: SoftUpdates stable?? In-Reply-To: <199805150721.IAA08488@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG try making tmp softupdates rather than sync (it's better because softupdates can decide that a deleted file never nneds to be written (it cancels the write) whereas async will write the block anyhow for no reason.) I will admit that my test machine has not been running X11 I will correct that oversight tomorrow On Fri, 15 May 1998, Brian Somers wrote: > 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. > > 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 , , > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message