Re: [PATCH] openat-die: use _Noreturn markup

Glad you found the root of the problem, and that it's not in gnulib. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

Re: rm -rf calls rmdir() prior to close(), which can fail

Jim Meyering wrote: >> Here is the patch that I expect to push tomorrow: ... > I've fixed/improved the ChangeLog/commit-log: > > Subject: [PATCH] fts: close parent dir FD before returning from > post-traversal fts_read > > The problem: the fts-using "mkdir

Re: rm -rf calls rmdir() prior to close(), which can fail

Jim Meyering wrote: ... > Here is the patch that I expect to push tomorrow: > > Subject: [PATCH] fts: close parent dir FD before returning from > post-traversal fts_read > > The problem: the fts-using "rm -rf A/B/" would attempt to unlink A, > while a file descript

Re: rm -rf calls rmdir() prior to close(), which can fail

= 0 unlinkat(AT_FDCWD, "a", AT_REMOVEDIR) = 0 close(0)= 0 close(1) = 0 close(2)= 0 Here is the patch that I expect to push tomorrow: >From a11c49cd72a91c05a272e36ff5d3cd92675c

Re: "du -b --files0-from=-" running out of memory

Pádraig Brady <[EMAIL PROTECTED]> wrote: >>> I notice that argv_iter does a malloc() + memcpy() per entry. >>> Since the sources are already NUL terminated strings >>> perhaps it could just return a pointer to a getdelim >>> realloc'd buffer which was referenced in the argv_iterator struct. >> >> T

Re: "du -b --files0-from=-" running out of memory

Pádraig Brady <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Subject: [PATCH 1/2] argv-iter: new module >> >> * gl/lib/argv-iter.h: New file. >> * gl/lib/argv-iter.c: New file. >> * gl/modules/argv-iter: New file. > > Very useful module! > >

Re: "du -b --files0-from=-" running out of memory

Jim Meyering <[EMAIL PROTECTED]> wrote: > Eric Blake <[EMAIL PROTECTED]> wrote: >> According to Barry Kelly on 11/23/2008 6:24 AM: >>> I have a problem with du running out of memory. >>> >>> I'm feeding it a list of null-separated file names

Re: "du -b --files0-from=-" running out of memory

Eric Blake <[EMAIL PROTECTED]> wrote: > [adding the upstream coreutils list] > According to Barry Kelly on 11/23/2008 6:24 AM: >> I have a problem with du running out of memory. >> >> I'm feeding it a list of null-separated file names via standard input, >> to a command-line that looks like: >> >>

Re: mkdir -p and EROFS

Christopher Faylor <[EMAIL PROTECTED]> wrote: ... >>IMHO, it is the kernel's job to provide an informative and, above all, >>compatible-with-most-others errno value, unless there is a very >>good reason. The small extra expense of an lstat call (*but only upon >>failure with errno == EROFS*) doesn

Re: mkdir -p and EROFS

Paul Eggert <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] (Eric Blake) writes: >> The algorithm change between 5.3.0 and 5.90 in lib/mkdir-p.c to >> try mkdir() first instead of stat(), and key off of EEXIST, breaks >> when mkdir() fails with EROFS on an intermediate directory when >> the writable

Re: mkdir -p and EROFS

[EMAIL PROTECTED] (Eric Blake) wrote: > The algorithm change between 5.3.0 and 5.90 in lib/mkdir-p.c to > try mkdir() first instead of stat(), and key off of EEXIST, breaks > when mkdir() fails with EROFS on an intermediate directory when > the writable directory has been mounted inside a read-only

Re: ls when acl() is busy

[EMAIL PROTECTED] (Eric Blake) wrote: ... > Hmm - murky waters here. It would be a simple one-line fix to > coreutils/lib/acl.c to ignore EBUSY as a non-error, and POSIX has > no requirements per se that a failure of acl() should imply a failure > of ls(1). Should a busy file be conservatively tr

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

Eric Blake <[EMAIL PROTECTED]> wrote: > Relevant clips from this cygwin bug report. When tty settings are weird > (I'm not sure whether the bug is in cygwin, xterm, or just bad tty > settings that could be reproduced elsewhere), backspace only repositions > the cursor on screen, so that the actual

Re: mkdir -p and network drives

>> By the way, the coreutils anon CVS mirror syncronization >> appears to be hung again, I've just sync'd things. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: Path confusion

Eric Blake <[EMAIL PROTECTED]> wrote: > How about it - does it make sense to add an --xdev option to all of the > recursive descent tools (chown, chmod, ls, ...) to force the recursion to > stop at mount points, or is find/xargs the only supported idiom for this? It's seductive, but I don't think

Re: cygwin 1.5.3: "/bin/mv dir dir" results in recursive-loop copy

Tony Clayton <[EMAIL PROTECTED]> wrote: > in cygwin 1.5.3, I got the following error after a moment: > mv: cannot create directory `src/src/src/src/src/src/src [...] /src': > Invalid argument mv (from any recent coreutils package) works fine in that case on unix systems. > I think it is t