From owner-freebsd-questions Fri Jan 17 12:40:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA24433 for questions-outgoing; Fri, 17 Jan 1997 12:40:05 -0800 (PST) Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA24376 for ; Fri, 17 Jan 1997 12:40:00 -0800 (PST) Received: from psy219.psy.msu.edu (psy219.psy.msu.edu [35.8.64.167]) by eyelab.psy.msu.edu (8.8.3/8.8.3) with SMTP id PAA13761 for ; Fri, 17 Jan 1997 15:45:10 -0500 (EST) Message-Id: <3.0.1.32.19970117154338.006c9554@eyelab.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: Windows Eudora Pro Version 3.0.1 beta 7 (32) Date: Fri, 17 Jan 1997 15:43:38 -0500 To: questions@freebsd.org From: Gary Schrock Subject: find in security check (was Re: vapour security check output) In-Reply-To: <87u3og6p4t.fsf@luddite.org> References: Will Mitayai Keeso Rowe's message of Fri, 17 Jan 1997 02:10:28 -0500 (EST) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 03:08 PM 1/17/97 -0500, you wrote: >Yeah, the 'find' in /etc/security uses the -X flag since it pipes into >xargs after the sort. You could substitute the following for the >offending while-loop: Hmm, this is sorta unrelated to the other question, but is there any way to make that find command not use up large amounts of memory? I was watching it the other night to figure out why the security script was killing the performance of the mud that runs on the machine I do some stuff for, and between a 39 meg mud task and the find task running at least as large at 9 megs or more, it's causing the machine to start swapping like crazy. Not exactly conducive to quick response on the mud. Gary Schrock root@eyelab.msu.edu