Thinking about how to make thread-safe the directory-creating parts
of cp -r, mv, tar, cpio, and even mkdir -p (i.e., don't change
the initial working directory), while remaining efficient even for
deep hierarchies, I realized that we need a new function, mkdirat,
which I've just checked in to
Roland McGrath [EMAIL PROTECTED] wrote:
I think that the Solaris *at functions were really primarily intended for
use with O_XATTR to get at file attribute magic pseudo-directories rather
than to optimize use of normal directories and files. Probably mkdirat
doesn't make sense in Solaris
Roland McGrath [EMAIL PROTECTED] wrote:
So I guess the exec*at business would ultimately be more complicated,
with two file descriptor parameters: one identifying the working
directory, and another by which to interpret the first parameter
if it's a relative file name.
It seems adequate to
I think that the Solaris *at functions were really primarily intended for
use with O_XATTR to get at file attribute magic pseudo-directories rather
than to optimize use of normal directories and files. Probably mkdirat
doesn't make sense in Solaris attribute pseudo-directories. But mkdirat is
as
On Wed, Nov 30, 2005 at 09:53:53PM +0100, Jim Meyering wrote:
I haven't looked too closely at find, but its -execdir predicate
makes me think having exec*at functions would be useful, too.
Only slightly. POSIX requires that -exec should happen with the
working directory the same as it was
