Date: Fri, 17 Jan 1997 15:43:38 -0500 From: Gary Schrock <root@eyelab.psy.msu.edu> To: questions@freebsd.org Subject: find in security check (was Re: vapour security check output) Message-ID: <3.0.1.32.19970117154338.006c9554@eyelab.msu.edu> In-Reply-To: <87u3og6p4t.fsf@luddite.org> References: Will Mitayai Keeso Rowe's message of Fri, 17 Jan 1997 02:10:28 -0500 (EST) <Pine.BSI.3.95.970117020615.1500C-100000@dreamlabs.dreaming.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.1.32.19970117154338.006c9554>