GNU bug report logs - #32291
Fwd: ls -ltcr and ls -lrt report different modification dates

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32291 in the body.
You can then email your comments to 32291 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Tolhurst-Cleaver <ludovic.tolhurst-cleaver <at> sabstt.com>
To: bug-coreutils <at> gnu.org
Subject: Fwd: ls -ltcr and ls -lrt report different modification dates
Date: Fri, 27 Jul 2018 10:48:40 +0100

Apologies - here is the OS information:

$ cat /proc/version
Linux version 3.10.0-862.3.3.el7.x86_64 
(builder <at> kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 
4.8.5-28) (GCC) ) #1 SMP Fri Jun 15 04:15:27 UTC 2018

Many thanks
LTC

-------- Forwarded Message --------

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

Message #8 received at 32291 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Ludovic Tolhurst-Cleaver <ludovic.tolhurst-cleaver <at> sabstt.com>,
 32291 <at> debbugs.gnu.org
Subject: Re: bug#32291: Fwd: ls -ltcr and ls -lrt report different
 modification dates
Date: Fri, 11 Jan 2019 01:41:40 -0700

tags 32291 notabug
close 32291
stop

Hello,

Seems your message was not replied to in 6 months - sorry about that.

On 2018-07-27 3:48 a.m., Ludovic Tolhurst-Cleaver wrote:
> 
> `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

The manual explains the "-c" option:
===
$ ls --help
  -c                 with -lt: sort by, and show, ctime (time of last
                     modification of file status information);
===

What you are seeing is the file's status-change timestamp (with "-c")
versus the file's content modification timestamp (without "-c").
You can view all timestamps at once with:
   stat ludo*

As such, I'm closing this as "not a bug", but discussion can continue
by replying to this thread.

regards,
 - assaf

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.