[bug #44569] find newermt cannot figure out how to interpret some dates.

[Eric Blake]

Update of bug #44569 (project findutils):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

This is not a bug in find.

https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#The-date-command-is-not-working-right_002e

The find command shares the same date parser as used in coreutils' date(1) -
and that parser honors daylight savings rules of your current locale.  As you
apparently live in a locale where that specific date in October has no
midnight (jumping straight from 23:59 on the previous day to 1:00 on that
day), then the date you have specified really is bogus.  Try specifying a time
that includes a safer hour, such as noon, that is unlikely to not exist due to
daylight savings jumps, or try using TZ=UTC to force a time zone that doesn't
have daylight savings issues.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44569>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/