Manage services on the current virtual computer.
Usage:
service list
service status <name>
service create <name> <product> --port <1-65535> [--bind <IPv4>]
[--executable <absolute-path|legacy>] [--user <local-user>]
[--advertise-version <true|false>] [--set <key=value> ...]
service configure <name> [--bind <IPv4>] [--port <1-65535>]
[--executable <absolute-path|legacy>] [--user <local-user>]
[--advertise-version <true|false>] [--set <key=value> ...]
service start <name>
service stop <name>
service remove <name>
All local users may inspect; local root is required for changes regardless
of this command's executable mode. Names are case-sensitive and unique per
computer (1-32 letters, digits, dots, underscores, or hyphens).
Products: mds-sshd supports permit_root_login=true or false (default true).
mds-echo uses bounded text requests. Its max_bytes option defaults to 1024 and
accepts 1-4096. Bind defaults to 127.0.0.1 (local only); use an assigned IPv4
address or 0.0.0.0 for all local addresses. Configuration may be made while
interfaces are down. A computer supports at most 64 instances.
Configuration lives in /etc/services/<name>.json on this virtual machine.
Edit it with write, or use service configure while the instance is stopped.
Starting loads and validates the file. A running service keeps its settings
until it is stopped and started again. File permissions control direct edits.
By default, an instance uses its product behavior. To run an installed
service program, select its absolute path with --executable and choose a
local --user. The default user is root and must have read/execute access to
the program and traversal access to its parent directories. The program must
provide the instance's service product. Clear the selection with
--executable legacy.
advertise_version defaults to true. Set it to false to hide the service
version from nmap -sV. SSH still authenticates the requested local account
on the target computer.
Creation starts stopped. Stop before configuring or removing. Running
wildcard/specific listeners on the same TCP port conflict. Different specific
addresses may share a port. Repeated start/stop is harmless. Catalog defaults
do not change existing configuration. State survives reconnects and reloads.
Example:
service create echo-test mds-echo --bind 127.0.0.1 --port 7000
service start echo-test
ss -ltn
service stop echo-test
service configure echo-test --port 7001 --set max_bytes=512
Use ss -ltn to inspect listeners. Listeners are simulated machine state.
MERIDIAN DATA SYSTEMS // TERMINAL
service
No topics match that search.