From owner-freebsd-questions Sun Oct 29 21:29:39 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA04382 for questions-outgoing; Sun, 29 Oct 1995 21:29:39 -0800 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA04377 for ; Sun, 29 Oct 1995 21:29:35 -0800 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id FAA02860 ; Mon, 30 Oct 1995 05:15:05 GMT To: chris warth cc: questions@freebsd.org Subject: Re: questions about 'update' In-reply-to: Your message of "Sun, 29 Oct 1995 18:08:14 PST." <199510300208.SAA00316@scooter.artemis.com> Date: Mon, 30 Oct 1995 05:15:02 +0000 Message-ID: <2858.815030102@palmer.demon.co.uk> From: Gary Palmer Sender: owner-questions@freebsd.org Precedence: bulk chris warth stands accused of writing in message ID <199510300208.SAA00316@scooter.artemis.com>: >I found the place where the 'update' frequency is set. That's the >first question - why is it so hard to change the frequency of update? >Can I just disable it in the kernel and go back to using a specialized >process in user space? sysctl -a on my box reveals: kern.update = 30 As Jordan, Soren and myself played with this number a bit in a fit of madness after a long day at CeBIT, I know that it works :-) To alter it: sysctl -w kern.update= I would think that setting it to zero is NOT a good idea :-) Gary