From owner-freebsd-audit Thu Nov 2 19: 9:33 2000 Delivered-To: freebsd-audit@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 4365C37B4C5; Thu, 2 Nov 2000 19:09:31 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA83624; Thu, 2 Nov 2000 22:09:28 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20001102182202.A26341@citusc17.usc.edu> References: <20001102182202.A26341@citusc17.usc.edu> Date: Thu, 2 Nov 2000 22:09:26 -0500 To: Kris Kennaway From: Garance A Drosihn Subject: Re: sort(1) tempfile patch Cc: Mike Heffner , audit@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:22 PM -0800 11/2/00, Kris Kennaway wrote: > Why's that? Your method has one fewer inode in /tmp, but many more files in /tmp directory. (directly in /tmp, as opposed to "some subdirectory of /tmp"). If sort is going to create multiple temp files, then your strategy puts all of those files in /tmp. I'd rather have one file in /tmp, and then lots of sort-related files in /tmp/sort.random for each user doing a sort. On a multi-user system (one which actually has multiple active users), one person doing a sort can cause a lot of "pollution" of /tmp, along with constant locking as those temporary files are created and destroyed. Also, I like the idea of having to be paranoid only for the creation of one directory, instead of having to be paranoid for every file created. -- --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message