# Convention: SMF manifests

illumos uses **SMF** (Service Management Facility), not systemd. A package that
ships a daemon ships an SMF manifest, not a `.service` unit.

## The shape

- Services are named by **FMRI**: `svc:/<category>/<name>:<instance>`,
  e.g. `svc:/network/ssh:default`.
- A **manifest** (XML) declares the service, its instances, dependencies,
  and the **method scripts** (start/stop/refresh).
- States: `disabled`, `offline`, `online`, `maintenance`, `degraded`. SMF
  restarts a failed service and tracks dependencies so order is automatic.

## Everyday commands

```
svcs                         # list services + states
svcs -xv                     # explain what's broken and why
svcadm enable  svc:/.../x    # bring online (and keep enabled across boots)
svcadm disable svc:/.../x
svcadm restart svc:/.../x
svccfg -s svc:/.../x ...     # edit properties / import a manifest
svccfg import your.xml       # install a manifest
```
Logs: `/var/svc/log/<fmri-with-slashes-as-dashes>.log`.

## For packagers

Ship the manifest in `$out` and document the import step. Don't translate a
systemd unit mechanically — model the dependencies in SMF's terms. The handbook
chapter <https://solnix.io/handbook/smf> is the reference.