FHS
First High-School Education Group Co., Ltd.
stock NYSE

Therefore, you must execute \`PATH=$PATH:/sbin\` to ensure the installation script runs to completion. The fundamental reason for this lies in Debian's strict separation between "system administration paths" and "ordinary user paths."
Why is it necessary to manually add \`/sbin\`?
The Role of \`/sbin\`:
Within the Linux Filesystem Hierarchy Standard (FHS), \`/sbin\` houses "System Binaries"—executable files intended for use by the system administrator (root)—such as \`ldconfig\`, \`fdisk\`, \`ip\`, and others.
Debian's Permissions Philosophy:
By default, the \`$PATH\` environment variable for ordinary users in Debian includes only directories like \`/usr/bin\` and \`/bin\`. Even in Debian 13 (Trixie)—which has implemented the "Merged-usr" scheme (meaning \`/sbin\` is effectively a symbolic link to \`/usr/sbin\`)—an ordinary user's shell still does not search these directories by default.
The Installation Script's "Probing" Behavior:
The IBKR \`.sh\` installer is, in essence, a self-extracting shell script. During its execution, it invokes various low-level utilities to probe and verify your system environment. A common scenario involves the script calling \`ldconfig\` to update or check the dynamic linker cache.
If \`/sbin\` is missing from the \`$PATH\` variable, the script will throw a "command not found" error when it attempts to execute \`ldconfig\`.
Some scripts are not written with sufficient rigor; instead of using absolute paths (e.g., \`/sbin/ldconfig\`), they simply specify the command name directly. This oversight leads to installation interruptions or errors.

Therefore, you must execute \`PATH=$PATH:/sbin\` to ensure the installation script runs to completion. The fundamental reason for this lies in Debian's strict separation between "system administration paths" and "ordinary user paths."
Why is it necessary to manually add \`/sbin\`?
The Role of \`/sbin\`:
Within the Linux Filesystem Hierarchy Standard (FHS), \`/sbin\` houses "System Binaries"—executable files intended for use by the system administrator (root)—such as \`ldconfig\`, \`fdisk\`, \`ip\`, and others.
Debian's Permissions Philosophy:
By default, the \`$PATH\` environment variable for ordinary users in Debian includes only directories like \`/usr/bin\` and \`/bin\`. Even in Debian 13 (Trixie)—which has implemented the "Merged-usr" scheme (meaning \`/sbin\` is effectively a symbolic link to \`/usr/sbin\`)—an ordinary user's shell still does not search these directories by default.
The Installation Script's "Probing" Behavior:
The IBKR \`.sh\` installer is, in essence, a self-extracting shell script. During its execution, it invokes various low-level utilities to probe and verify your system environment. A common scenario involves the script calling \`ldconfig\` to update or check the dynamic linker cache.
If \`/sbin\` is missing from the \`$PATH\` variable, the script will throw a "command not found" error when it attempts to execute \`ldconfig\`.
Some scripts are not written with sufficient rigor; instead of using absolute paths (e.g., \`/sbin/ldconfig\`), they simply specify the command name directly. This oversight leads to installation interruptions or errors.