Hi,
as reported in https://bugzilla.redhat.com/show_bug.cgi?id=1141368 ,
there is a possible race condition in mv in the case of hardlinks.
Bug is reproducible even on ext4 filesystem (I guess it is filesystem
independent), even with the latest coreutils. There was already attempt
to fix the
Bob Proulx wrote:
Gian Ntzik wrote:
It seems that using rm -r with a path that goes into a (non-empty)
directory intended for removal (and back up e.g. using dot-dots) fails
to remove the directory. The directory is rendered empty, but itself not
removed.
For example,
$ mkdir -p /tmp/a/b/c
$
unarchive 17553
forcemerge 17553 18503
stop
On 09/19/2014 12:17 AM, Linda A. Walsh wrote:
gemfield wrote:
Hi,
I am running ls -lsh on kubuntu 14.04, here is the output:
gemfield@gemfield-ThinkPad-Edge:~$ ls -ls
4 -rw-rw-r-- 1 gemfield gemfield9 9 18 23:12 test
forcemerge 18159 18479
stop
On 09/15/2014 12:08 AM, 積丹尼 Dan Jacobson wrote:
$ date -d 'today + month'
Wed Oct 15 07:04:59 CST 2014
$ date -d 'today - month'
Wed Oct 15 07:05:05 CST 2014
This is essentially the same as issue http://bugs.gnu.org/18159
for which I outlined a possible solution.
tag 18500 notabug
close 18500
stop
On 09/18/2014 02:33 PM, Philipp Thomas wrote:
The testsuite of coreutils 8.22 is failing on s390. Can anybody help me
pinpointing the culprit?
Here is the relevant part of the log:
FAIL: tests/misc/shuf-reservoir
===
+
Bob Proulx b...@proulx.com writes:
Gian Ntzik wrote:
It seems that using rm -r with a path that goes into a (non-empty)
directory intended for removal (and back up e.g. using dot-dots) fails
to remove the directory. The directory is rendered empty, but itself not
removed.
For example,
Linda A. Walsh coreut...@tlinx.org writes:
Bob Proulx wrote:
Gian Ntzik wrote:
It seems that using rm -r with a path that goes into a (non-empty)
directory intended for removal (and back up e.g. using dot-dots) fails
to remove the directory. The directory is rendered empty, but itself not
On 09/19/2014 12:17 AM, Linda A. Walsh wrote:
gemfield wrote:
4 * 1K blocks = 4.0K blocks.
^^ - bytes
I think the ambiguity is that there is no unit output.
With the human output options, bytes are the implicit unit rather than blocks.
Those darn trees! Can't
