From owner-freebsd-questions Fri Jan 21 2:49:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 74AB11547D for ; Fri, 21 Jan 2000 02:49:10 -0800 (PST) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12Bbby-000KJ4-00; Fri, 21 Jan 2000 12:48:14 +0200 Date: Fri, 21 Jan 2000 12:48:14 +0200 From: Neil Blakey-Milner To: Dan Langille Cc: questions@FreeBSD.ORG Subject: Re: mktemp() possibly used unsafely; consider using mkstemp() Message-ID: <20000121124814.C77623@mithrandr.moria.org> References: <200001210902.WAA73869@ducky.nz.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001210902.WAA73869@ducky.nz.freebsd.org> Organization: Rhodes University Computer Users' Society X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-01-21 (22:02), Dan Langille wrote: > syscall.o: In function `do_mktemp': > syscall.o(.text+0x2e1): warning: mktemp() possibly used unsafely; > consider using mkstemp() > > Two machines, both on 3.3-19991207-SNAP, both building rsync-2.3.2, > one suceeds, the other gets the above. Go figure. > > Clues please. It's not a fatal error. There is most probably another reason for the failure. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message