|
From: | Ludovic Tolhurst-Cleaver |
Subject: | bug#32289: ls -ltcr and ls -lrt report different modification dates |
Date: | Fri, 27 Jul 2018 10:41:50 +0100 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
Dear GNU folks I believe I have found a bug in ls in the GNU coreutils v. 8.22. My colleague and I found that 'ls' reported a different date for a gzipped log file when run with different options in a directory containing a large amount of data (1000MB). In the full listing we saw that date next to a different file in the other listing. `ls -ltcr` seems to be the one showing the correct date here. I like to use `ls -ltc` because it's my initials. My colleague was running `ls -lrt`. $ ls -ltcr ludo* -rw-rw-rw- 1 pax pax 237817 Jul 20 06:53 ludovic.tolhurst-cleaver_sabstt.com-log-20180720.gz $ ls -lrt ludo* -rw-rw-rw- 1 pax pax 237817 Jul 18 12:30 ludovic.tolhurst-cleaver_sabstt.com-log-20180720.gz I'm afraid I do not have the capability to test this on any later version of the coreutils. Thanks & regards Ludo Tolhurst-Cleaver Perl Developer SABS TT
[Prev in Thread] | Current Thread | [Next in Thread] |