From owner-freebsd-current Sat Jun 10 3: 7:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 6463A37BCB7 for ; Sat, 10 Jun 2000 03:07:49 -0700 (PDT) (envelope-from drosih@rpi.edu) 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 GAA107118 for ; Sat, 10 Jun 2000 06:07:46 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3941842C.DE59BF21@vangelderen.org> References: <3941842C.DE59BF21@vangelderen.org> Date: Sat, 10 Jun 2000 06:08:08 -0400 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: mktemp() patch Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It's probably better to just get rid of the PID and use randomness >throughout the name than to use 72 characters. 64^6 vs. 2*(72^3) . I seem to be in the minority on this, but in general I *like* the idea that the tempfiles include the pid. It's bad because it makes it easier for an evil-person to guess what the next tempfile will be, but it's nice in after-the-fact situations, where there are a bunch of tempfiles left over, and you're wondering which ones are related (in the sense of having come from the same process, and you can then check if the process is still running). Not a big issue for me, as I doubt I have taken advantage of this more often than about once every two years, but I thought I would at least mention it. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message