Eenos Command-line Tools
Find all installed Eenos administrative scripts with their command-line options, usage, requirements and operational effects.
The Eenos scripts live in /usr/local/eenos/scripts/. This reference covers 68 administrative scripts, including internal helpers. Dummy development files and bytecode-cache directories are excluded.
Browse commands
| Group | Scripts |
|---|---|
| Backup & Restore | 7 |
| Service Setup | 19 |
| Runtimes & Sandboxes | 8 |
| Account & Server Maintenance | 19 |
| DNS Tools | 4 |
| Administration & Internal Tools | 11 |
Before running a command
Use a root shell on the target Eenos server unless a page states otherwise. The wrappers use the installed Eenos Python environment; they are not standalone Python packages to install with pip. Use full paths so that your shell selects the intended command.
Read the target scope and operational effects before executing an example. Replace usernames, domains, IDs, runtime identifiers and paths. Quoted examples preserve spaces; they do not make an untrusted value safe for legacy helpers that assemble shell commands. Keep configuration/data backups appropriate to the action.
Help and option conventions
Modern parsers expose -h/--help; legacy scripts can use fixed positional forms instead. Some scripts have no option parser and run immediately, including setup and collection helpers. Their reference pages identify this explicitly: do not run every script with --help to discover options.
Flags such as --demon, and command names such as sanboxpython, httpdmodmanger and siteoptimizor, preserve the actual installed spellings. A tool accepting a version identifier does not establish that the corresponding package is available for your operating system.
Results and logs
Read operation output and verify the affected account, service or artifact. Legacy wrappers do not all propagate handler failures into their exit status. Background launch is not completion, and stopping a task does not roll back earlier writes.
Many administrative tools use /var/log/eenos/eenos.log; backup, restore, migration and scanner operations also use dedicated logs identified in their references. Treat login links, credentials, backups and diagnostic output as private.
License Management
License administration has its own License Management section, immediately after Getting Started. Its binary is installed under /usr/local/eenos/bin/, outside the scripts inventory above.
Migration converters
The separately installed cptoeenos/cp2eenos and datoeenos/da2eenos remain under Migration. They are not part of the 68 administrative scripts counted here. See restoreacct for the destination restore command.
For the local read-only account/package/domain inventory interface, use the EAPI command-line API reference. Its binary is /usr/bin/eapi; it is separate from the administrative scripts counted here.