On Fri, Feb 16, 2024 at 11:11:09AM -0600, David Wright wrote: > On Fri 16 Feb 2024 at 09:12:24 (-0500), Greg Wooledge wrote: > > On Fri, Feb 16, 2024 at 03:34:12PM +0200, Anssi Saari wrote: > > > Yah. It was ssh passing through all that. On serial console, locale > > > settings are as expected: > > > > > > $ locale > > > LANG=en_US.UTF-8 > > > LANGUAGE=en_US:en > > > LC_CTYPE="en_US.UTF-8" > > > LC_NUMERIC="en_US.UTF-8" > > > LC_TIME="en_US.UTF-8" > > [...] > > > > Well then, that just changes the mystery from "happens on the Debian > > system I ssh into" to "happens on my ssh client". For some reason, > > your ssh client has all of those LC_* variables set in its environment, > > which is still quite unusual. > > Could something weird here do that? > > $ grep LC /etc/ssh/*g > /etc/ssh/ssh_config: SendEnv LANG LC_* > /etc/ssh/sshd_config:AcceptEnv LANG LC_* > $
That's all normal and expected. What's odd is that client *actually has* LC_NUMERIC and so on set in its environment. Which... is not a problem if they're all set to the correct values. It's weird, but not wrong. The problem for the OP was that one of the values was not set correctly, or at least not as expected. At this point we have no idea whether the ssh client is even a Unix/Linux system. It could be anything. It could be a literal toaster.
