Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Hannu E K Nevalainen (garbage mail)" <garbage_collector AT telia DOT com>
To:	<cygwin AT cygwin DOT com>
Cc:	<dmay AT tvi DOT edu>
Subject:	RE: Problem with database engine on Cygwin
Date:	Thu, 10 Apr 2003 00:15:34 +0200
Message-ID:	<NGBBLLIAMFLGJEOAJCCEEEBACOAA.garbage_collector@telia.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
In-Reply-To:	<200304091950.h39Jo0kx029631@phys-nfs1.tvi.cc.nm.us>
X-MIMEOLE:	Produced By Microsoft MimeOLE V5.00.2615.200
Importance:	Normal

> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of dmay AT tvi DOT edu

> I worked around the issue in my code by closing the offending
> file, renaming
> it to a 20 character pseudo-random string and then deleting it.
> When I did
> that, I had no problem creating another file with the same name.
> The problem
> here is if I happen to get 2 20-character psuedo-random strings that are
> identical (not likely, I know), this is going to fail.
>
> So, I kludged it in a somewhat unclean, albeit functional, way.  Is there
> another workaround that is a little more elegant?


Might it be that this helps?

 $ man 3 mktemp


/Hannu E K Nevalainen, Mariefred, Sweden
--
...
PORTABILITY
       ANSI C does not require either `mktemp'  or  `mkstemp';  the  System
V
       Interface Definition requires `mktemp' as of Issue 2.

          Supporting OS subroutines required: `getpid', `open', `stat'.
...
	mktemp is part of the libc library.
...
	info libc

--END OF MESSAGE--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -