653
edits
Changes
From SME Server
Jump to navigationJump to search→Known issue 3: migration of contribs that start services requires consideration of startup methods
With the introduction of systemd there are different and '''mutually exclusive''' options to start (and monitor) services.
With the introduction of systemd there are different and '''mutually exclusive''' options to start (and monitor) services.
* Old way: as long as <code>/etc/rc.d/rc7.d/S??contrib</code> exists, the bootstrap console will start the service as in versions previous to 10.
* Old way: as long as <code>/etc/rc.d/rc7.d/S??contrib</code> exists, the bootstrap console will start the service as in versions previous to 10.
* New way: if you want to use systemd simply remove <code>/etc/rc.d/rc7.d/S??contrib</code> and ensure that your event uses a valid signal for systemd: once is NOT understood by sytemd.
* New way: if you want to use systemd simply remove <code>/etc/rc.d/rc7.d/S??contrib</code> and ensure that your event uses a valid signal for systemd: <code>once</code> is NOT understood by sytemd.
These conflict, so choose one way or the other.
These conflict, so choose one way or the other.
