On 25.04.1 terminal input to the TrueNAS “cli” command over ssh runs like a 300 baud modem. Output is fine, and outside of cli the ssh session performs as expected. Is this a known issue, or maybe it is intentional to discourage hacking?
Evan
On 25.04.1 terminal input to the TrueNAS “cli” command over ssh runs like a 300 baud modem. Output is fine, and outside of cli the ssh session performs as expected. Is this a known issue, or maybe it is intentional to discourage hacking?
Evan
This is terrible. happening to me too.
launching “cli” (what a terrible naming) → takes 7 seconds for cli to open.
Then every keypress is delayed
Im on a very good hardware:
64Gb ddr5 ECC, AMD EPYC 8024P 8-Core Processor, CPU is barely loaded - at 1-2%.
it’s some kind of a bug in truenas scale.
Suggest you file it as one then.
Why is the naming terrible? CLI, Command Line Interface
Naming your CLI command cli
is like naming your dog “dog” and then yelling “dog!” at a crowded dog park—good luck figuring out which one is yours.
It’s peak chaos. It’s the command-line equivalent of calling your app “app” or your file “file.txt” in a directory full of files. Bonus points for the sheer thrill of trying to Google “cli error in cli” and watching your soul slowly exit your body.
Please. Give it a real name. Your future self (and everyone else) will thank you.
Bug raised: Jira
Yeah, you definitely wouldn’t include the name of the product you’re using in that search.
And the TrueNAS menu is called cli_console.