Date: Fri, 12 May 2000 17:48:41 +0400 (MSD) From: "Aleksandr A.Babaylov" <babolo@links.ru> To: kris@FreeBSD.ORG (Kris Kennaway) Cc: K.J.Koster@kpn.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Double buffered cp(1) Message-ID: <200005121348.RAA20140@aaz.links.ru> In-Reply-To: <Pine.BSF.4.21.0005120016210.79006-100000@freefall.freebsd.org> from "Kris Kennaway" at "May 12, 0 00:18:10 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway writes: > On Fri, 12 May 2000, Koster, K.J. wrote: > > > Unless this has been changed from 3.4 to 4.0, gcc defaults to /var/tmp. I > > never understood why, and the gcc manual page claims that it's /tmp (I > > think). MFS users, synchronize your TMPDIR variables ... now. :-) > > It did. > > Compiling a simple test program just now shows: > > + -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccl22910.i > + -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccc22910.s > + -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccP22910.o > - -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccl22910.i > - -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccc22910.s > - -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccP22910.o > > (incidentally, another reason to use -pipe is that the above filenames are > predictable and probably handled insecurely so that another user can cause > any of your files to be overwritten when you compile something. This is > on my list of things to fix). Just use own subdirectory in /tmp with some anticrackers manoevres. see PR bin/18275 and http://www.links.ru/FreeBSD/mkinittmpdir/ which do this work. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005121348.RAA20140>