nethsm-health-state(1)
π nethsm-health-state(1) β like, the manual page bestie
Okay so real talk: this is the nethsm-health-state(1) page from the General Commands Manual, and honestly? It's a short one. We're talking snack-sized. Let me walk you through it, no cap.
β¨ NAME β¨
nethsm-health-state β the "netshm health state" command. That's the whole name section. Short and sweet, we love a minimal queen π
πΈ SYNOPSIS πΈ
Here's the vibe, verbatim, don't @ me:
nethsm health state [-a|--auth-passphrase-file] [-c|--config]
[-l|--label] [-u|--user] [-h|--help]
That's it. That's the whole invocation. Every flag optional, all cute and bracketed π¦
π DESCRIPTION π
The "netshm health state" command.
Yeah. That's literally the entire description in the original. It's giving mysterious, it's giving main character who refuses to explain herself π I'm not gonna invent lore for you β that's all the page says, so that's all I'm saying too.
π₯ OPTIONS π₯
Every single one, in order, nothing skipped, periodt:
-a,--auth-passphrase-file <AUTH_PASSPHRASE_FILE>β the path to a file containing a passphrase for authentication. The passphrase in that file has to be the one for the user you picked for the command β no mixing and matching, bestie π«Ά
This option can be provided multiple times, which you need for commands that require multiple roles at once. And with multiple passphrase files, ordering matters β the files get assigned to the respective user provided by the --user option, so keep your lineup correct or it's chaos π
May also be specified with the NETHSM_AUTH_PASSPHRASE_FILE environment variable. Slay.
-c,--config <CONFIG>β the path to a custom configuration file. If you specify it, that custom config file gets used instead of the default configuration file location. Simple as that β¨
May also be specified with the NETHSM_CONFIG environment variable.
-l,--label <LABEL>β a label uniquely identifying a device in the configuration file. Must be provided if there's more than one device set up in the configuration file β like, if you've got multiple devices and you don't label, you're in your flop era π
May also be specified with the NETHSM_LABEL environment variable.
-u,--user <USER>β a user name which is used for a command. You can provide it if no user name is set up in the configuration file for a device. You must provide it if several user names of the same target role are set up in the configuration file for a device. Read that twice, it's a whole conditional situation π₯
This option can be provided multiple times, which is needed for commands that require multiple roles at once.
May also be specified with the NETHSM_USER environment variable.
-h,--helpβ print help (see a summary with-h). Iconic, does exactly what it says on the tin π
Lowkey important vibe check: the environment variables above are alternatives to the flags, not extra flags. And the three "must be provided ifβ¦" conditions are real requirements β that's the original talking, not me being dramatic π
π§ and that's the page π§
That's genuinely everything β no BUGS section, no EXAMPLES, no SEE ALSO, nothing hiding at the bottom. We ate and left no crumbs because there were no crumbs to begin with π
Cute little sign-off for you: this was nethsm-health-state(1) from the nethsm-health-state source, footer stamped nethsm-health-state / nethsm-health-state(1) β no date, so don't come for me, I can only work with what I'm given ππ bye bestie, stay hydrated and keep your passphrase files in order! π
π¦ where this page comes from
- arch rolling: nethsm-cli 0.10.0-1 Β· Apache-2.0 OR MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms