From owner-freebsd-questions Mon Sep 30 03:29:58 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA02408 for questions-outgoing; Mon, 30 Sep 1996 03:29:58 -0700 (PDT) Received: from mail.EUnet.hu (mail.eunet.hu [193.225.28.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA02352 for ; Mon, 30 Sep 1996 03:29:54 -0700 (PDT) Received: by mail.EUnet.hu, id MAA02385; Mon, 30 Sep 1996 12:29:41 +0200 Received: by CoDe.CoDe.hu (LAA02475); Mon, 30 Sep 1996 11:41:23 GMT From: Gabor Zahemszky Message-Id: <199609301141.LAA02475@CoDe.CoDe.hu> Subject: Re: a freebsd testimonial To: freebsd-questions@freebsd.org Date: Mon, 30 Sep 1996 11:41:22 +0000 (GMT) Cc: owensc@enc.edu In-Reply-To: from "Charles Owens" at Sep 27, 96 12:38:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 3. A realization about quotas: I'd heard somewhere that > its a good idea to turn the quota system off (quotaoff) > before changing a user's quotas (edquota). I'd been > doing this in my adduser script and whenever I added > a user the system would crash shortly thereafter. > Apparantly some nasty system bug was being triggered. > Not toggling the quota system on and off before using > edquota got rid of a good portion of my system crashes. I don't know it very well, but as I know, after turning quota off, and before turning it on, you have to run the quotacheck command, to actualize the database. -- Gabor Zahemszky -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- Earth is the cradle of human sense, but you can't stay in the cradle forever. Tsiolkovsky