Hide Forgot
PREAMBLE: I know $TZ is not needed on a linux system, but at the end of this email I explain why I need to use it. I was not sure where to file this bug under: sh-utils (date) or glibc. PROBLEM: The weird output of the "date" command when $TZ is set in a certain way. DETAILS: 1) with an old caldera1.3/libc5 (all is ok) $ export TZ=CET-1CEST $ date Tue Jun 20 14:01:29 CEST 2000 $ 2) With redhat 6.1 (note the ` after CEST) $ date Tue Jun 20 14:08:13 CEST 2000 $ export TZ=CET-1CEST $ date Tue Jun 20 14:08:18 CEST` 2000 $ 3) With beta1/2 (the timezone is gone) $ date mar giu 27 20:57:40 CEST 2000 $ export TZ=CET-1CEST $ date mar giu 27 20:57:46 2000 $ Is this new behavior the "normal behavior"? That is, is "TZ=CET-1CEST" something wrong for the new "date"/glibc included in beta1/2? BACKGROUND: We have a "legacy" unix application that runs on linux through iBCS (I now iBCS is deprecated...). This app wants us to set "TZ=CET-1CEST" to handle the time properly. We set TZ in the script that launches the app, so that usually TZ is unset. The app can give you a sub-shell. This sub-shell has obviously TZ set and shows the above problem. This app requires TZ=CET-1CEST, TZ=CET is not enough.
Even more bizarre: $ ( export TZ=CET-1CEST; date | cat -vet ) Wed Aug 2 13:07:30 ^A 2000$ It looks like the timezone is \001.
Seems like it's a glibc bug. Test case attached.
Created attachment 1794 [details] test case
Am testing a fix right now
Fixed in glibc-2.1.92-7