Re: ntpsec as server questions
On Mon 04 Dec 2023 at 16:24:11 (-0500), gene heskett wrote:
> On 12/4/23 11:31, Dan Purgert wrote:
> > On Dec 04, 2023, gene heskett wrote:
> > > [...]
> > > So here on coyote: date -u:
> > > Mon Dec 4 15:47:44 UTC 2023
> > > but on mkspi: date -u:
> > > Mon 04 Dec 2023 03:47:16 PM UTC
> > > [...]
> > >
> > > WTH? Where is that false 12 hour offset coming from?
> >
> > Coyote seems to use the standard output of 'date' (in 24-hour clock
> > format).
> >
> > mkspi /appears/ to be using an approximation of "-R" ("--rfc-email",
> > as set in RFC5322), though it's missing the comma between "Mon" and "04
> > Dec", and is set in 12-hour mode.
> >
> > It's been ages since I've dug into it, but I _BELIEVE_ the LC_TIME
> > environment variable has an effect here. (Or had, at some point in the
> > past).
> It might well be, Dan but no man page,
They're all documented together in man locale, with examples:
$ man locale | grep -A25 EXAMPLES
EXAMPLES
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
$ locale date_fmt
%a %b %e %H:%M:%S %Z %Y
$ locale -k date_fmt
date_fmt="%a %b %e %H:%M:%S %Z %Y"
$ locale -ck date_fmt
LC_TIME
date_fmt="%a %b %e %H:%M:%S %Z %Y"
$
Set for "C" in the env output.
> I redirected the /etc/localtime link to EST5EDT and fixed it, the
> thing thought it was in the 3rd worst hell hole in the US, LA, CA.
Please—no.
Cheers,
David.
Reply to: