On Saturday 20 November 2010 05:31:15 Grant Edwards wrote:
> On 2010-11-20, Peter Humphrey <[email protected]> wrote:
> > On Friday 19 November 2010 17:53:31 Grant Edwards wrote:
> >>
> >> What different behavior?
> >
> > As I said, from the command line ls shows the year for any file
> > more than 12 months old, in place of the time. When executed from
> > find it doesn't.
>
> I don't see any difference when I do it.
It turns out that the difference is in the 'c' switch to ls. With the
switch I get this (grepping for a single file of the many):
$ find . -iname \*.jpg -exec ls '-cdhl' {} \; | grep DSC_1810.JPG
-r-xr-xr-x 1 prh prh 3.7M Aug 11 17:32 ./images/BOH-2009/DSC_1810.JPG
and without it I get this:
$ find . -iname \*.jpg -exec ls '-dhl' {} \; | grep DSC_1810.JPG
-r-xr-xr-x 1 prh prh 3.7M Oct 28 2009 ./images/BOH-2009/DSC_1810.JPG
Perhaps some process I ran on 11 August this year touched the file
without modifying it. Anyway, it seems there isn't a problem (except in
my website[1] management techniques, perhaps). Thanks anyway.
$ equery l coreutils
* Searching for coreutils ...
[IP-] [ ] sys-apps/coreutils-8.7:0
[1] I don't suppose anyone's interested, but just in case, the site is
at <http://tideswellmvc.co.uk/>; It's been my baby for about 18 months.
--
Rgds
Peter. Linux Counter 5290, 1994-04-23.