From owner-freebsd-current Fri May 12 10:22:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id 6390D37BE6D; Fri, 12 May 2000 10:22:53 -0700 (PDT) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id KAA89686; Fri, 12 May 2000 10:22:52 -0700 (PDT) (envelope-from ab@astralblue.com) Date: Fri, 12 May 2000 10:22:52 -0700 (PDT) From: "Eugene M. Kim" To: "David O'Brien" Cc: Munehiro Matsuda , freebsd-current@FreeBSD.ORG Subject: Re: Small fix for compile error with internat crypto code In-Reply-To: <20000512090028.B18420@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 May 2000, David O'Brien wrote: | On Fri, May 12, 2000 at 06:34:08AM -0700, Eugene M. Kim wrote: | > I guess, although it could be fine if we had a flag to mkdir(1) that | > makes it just succeed when there's already a directory of the same name. | | Yes, that is "-p". | Oh yes you're right. But then things still remain strange... Isn't this: test -d openssl || mkdir -p openssl supposed to never give the `mkdir: openssl: File exists' error? So I guess the real cause of that bug is not a race condition between two mkdir -p commands. Haven't seen the error recently so can't exactly tell, but it looks more like there is already an `openssl' that isn't a directory. Eugene -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message