> In the debian/rules, there is an override so I suppose not starting it by default is on purpose since the service doesn't work if there is no config written.
>
> [debian/rules]
> override_dh_installinit:
> dh_installinit -pceph-iscsi --name rbd-target-api
> dh_installinit -pceph-iscsi --name rbd-target-gw
Hmm, the package structure looks weird to me. The override is to use a service name different from the package name, which makes sense. Then it will render the postinst script as:
To defer it to systemd. However, the package doesn't leverage dh_installsystemd with --no-enable and --no-start. Instead, it uses debian/ceph-iscsi.install to manually copy usr/lib/systemd/system/*.service to the system.
> In the debian/rules, there is an override so I suppose not starting it by default is on purpose since the service doesn't work if there is no config written. dh_installinit:
>
> [debian/rules]
> override_
> dh_installinit -pceph-iscsi --name rbd-target-api
> dh_installinit -pceph-iscsi --name rbd-target-gw
Hmm, the package structure looks weird to me. The override is to use a service name different from the package name, which makes sense. Then it will render the postinst script as:
==== systemd- native rbd-target-api $_dh_action || exit 1 systemd- native rbd-target-gw $_dh_action || exit 1
invoke-rc.d --skip-
...
invoke-rc.d --skip-
====
To defer it to systemd. However, the package doesn't leverage dh_installsystemd with --no-enable and --no-start. Instead, it uses debian/ ceph-iscsi. install to manually copy usr/lib/ systemd/ system/ *.service to the system.